# Managed container stuck in "Starting (Networking)" **URL:** \ **Category:** Rancher 1.x\ **Created:** [April 12, 2016, 11:48pm UTC](https://forums.suse.com/t/managed-container-stuck-in-starting-networking/2420 "2016-04-12T23:48:53Z")\ **Posts on this page:** 11\ **Page:** 1
**Author:** ![tchan](https://avatars.discourse-cdn.com/v4/letter/t/4bbf92/32.png) [@tchan](https://forums.suse.com/u/tchan)\ **Post date:** [April 12, 2016, 11:48pm UTC](https://forums.suse.com/t/managed-container-stuck-in-starting-networking/2420/1 "2016-04-12T23:48:53Z")
I just started with rancher 1.0 and am unable to get a managed networking container started. Tested this with Docker 1.10.3 on both Debian Jessie and CentOS 7. I start up rancher/server and add my host with no issue. I then try to “Add Container” in Infrastructure-\>Hosts on a specific host with no specific options other than the image and name. The “Network Agent” starts up and gets an IP. The container then show “Starting (Networking)” and doesn’t get past that. If I create the container with “Host” or “Container” or “None” network, it is fine. I’ve disabled ipv6 on the host machine but that didn’t help. I thought it might have been a conflict on the 10.42.0.0/16 subnet as I have some IPs in that range. After switching that in v1/settings/docker.network.subnet.cidr and remaking the environment, that didn’t help the issue either. Any ideas? ---
**Author:** ![denise](https://avatars.discourse-cdn.com/v4/letter/d/82dd89/32.png) [@denise](https://forums.suse.com/u/denise)\ **Post date:** [April 13, 2016, 4:14am UTC](https://forums.suse.com/t/managed-container-stuck-in-starting-networking/2420/2 "2016-04-13T04:14:17Z")
Can you provide the logs for your network? [http://docs.rancher.com/rancher/faqs/#where-can-i-find-logs-for-networking](http://docs.rancher.com/rancher/faqs/#where-can-i-find-logs-for-networking) Also, can you share the network agent logs from `docker logs`? ---
**Author:** ![tchan](https://avatars.discourse-cdn.com/v4/letter/t/4bbf92/32.png) [@tchan](https://forums.suse.com/u/tchan)\ **Post date:** [April 13, 2016, 6:30pm UTC](https://forums.suse.com/t/managed-container-stuck-in-starting-networking/2420/3 "2016-04-13T18:30:37Z")
/var/log/rancher-net.log or /var/log/charon.log do not exist in the rancher agent container nor in the “Network Agent” container that gets spawned. docker logs for the “Network Agent” is: INFO: Downloading agent [http://centos7ranchertest01v:8080/v1/configcontent/configscripts](http://centos7ranchertest01v:8080/v1/configcontent/configscripts) The system is going down NOW! Sent SIGTERM to all processes Sent SIGKILL to all processes Requesting system reboot INFO: Downloading agent [http://centos7ranchertest01v:8080/v1/configcontent/configscripts](http://centos7ranchertest01v:8080/v1/configcontent/configscripts) … repeat ---
**Author:** ![tchan](https://avatars.discourse-cdn.com/v4/letter/t/4bbf92/32.png) [@tchan](https://forums.suse.com/u/tchan)\ **Post date:** [April 19, 2016, 9:34pm UTC](https://forums.suse.com/t/managed-container-stuck-in-starting-networking/2420/4 "2016-04-19T21:34:49Z")
Any ideas about how to get this working? ---
**Author:** ![Gaurav\_Mehta](https://avatars.discourse-cdn.com/v4/letter/g/a698b9/32.png) [@Gaurav\_Mehta](https://forums.suse.com/u/Gaurav_Mehta)\ **Post date:** [April 20, 2016, 10:22pm UTC](https://forums.suse.com/t/managed-container-stuck-in-starting-networking/2420/5 "2016-04-20T22:22:27Z")
We seem to have be having the same issue as well. Rancher 1.0.0 Docker v1.10.2 RHEL v7.2 ---
**Author:** ![denise](https://avatars.discourse-cdn.com/v4/letter/d/82dd89/32.png) [@denise](https://forums.suse.com/u/denise)\ **Post date:** [April 25, 2016, 6:26pm UTC](https://forums.suse.com/t/managed-container-stuck-in-starting-networking/2420/6 "2016-04-25T18:26:48Z")
@tchan On the host, can you try running ```auto docker run tutum/curl curl http://centos7ranchertest01v:8080/v1/configcontent/configscripts ``` ---
**Author:** ![tchan](https://avatars.discourse-cdn.com/v4/letter/t/4bbf92/32.png) [@tchan](https://forums.suse.com/u/tchan)\ **Post date:** [May 2, 2016, 7:13pm UTC](https://forums.suse.com/t/managed-container-stuck-in-starting-networking/2420/7 "2016-05-02T19:13:52Z")
{“id”:“eb542099-9dc1-43c5-8f2d-1e12ae4190e6”,“type”:“error”,“links”:{},“actions”:{},“status”:404,“code”:“Not Found”,“message”:“Not Found”,“detail”:null} ---
**Author:** ![tchan](https://avatars.discourse-cdn.com/v4/letter/t/4bbf92/32.png) [@tchan](https://forums.suse.com/u/tchan)\ **Post date:** [May 4, 2016, 10:33pm UTC](https://forums.suse.com/t/managed-container-stuck-in-starting-networking/2420/8 "2016-05-04T22:33:41Z")
I need to do a bit more testing, but this might have been fixed after going to rancher 1.0.1. ---
**Author:** ![tchan](https://avatars.discourse-cdn.com/v4/letter/t/4bbf92/32.png) [@tchan](https://forums.suse.com/u/tchan)\ **Post date:** [May 4, 2016, 11:02pm UTC](https://forums.suse.com/t/managed-container-stuck-in-starting-networking/2420/9 "2016-05-04T23:02:44Z")
Correction: the rancher version running is latest (1.1.0-dev1). Added containers seem to start up correctly now on both a Debian Jessie and CentOS 7 box. ---
**Author:** ![QkiZMR](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/qkizmr/32/1441_2.png) [@QkiZMR](https://forums.suse.com/u/QkiZMR)\ **Post date:** [June 22, 2016, 2:00pm UTC](https://forums.suse.com/t/managed-container-stuck-in-starting-networking/2420/10 "2016-06-22T14:00:39Z")
I have same issue. load-balancer\_2, websocket-proxy\_1, websocket-proxy-ssl\_1, load-balancer-swarm\_1 stuck on Networking… ---
**Author:** ![bruno.galindro](https://avatars.discourse-cdn.com/v4/letter/b/3ec8ea/32.png) [@bruno.galindro](https://forums.suse.com/u/bruno.galindro)\ **Post date:** [December 4, 2016, 6:22pm UTC](https://forums.suse.com/t/managed-container-stuck-in-starting-networking/2420/11 "2016-12-04T18:22:03Z")
Same issue here. I’m using Rancher v1.1.4. This begin happen after I’ve restarted all Network Agent containers from all of my hosts.