moby: Unable to start container on docker 1.9.0: container already connected to network bridge

I have a simple Docker container (running the stock grafana/grafana image), and it ran perfectly on Docker 1.8.3; after upgrade to Docker 1.9.0, it will not start:

$ docker run --name grafana -v /data/grafana:/var/lib/grafana -e "GF_SERVER_ROOT_URL=https://fr-s-ccr-dock1.example.gov/grafana/" -e "GF_SECURITY_ADMIN_PASS=*********" -e "GF_USERS_ALLOW_SIGN_UP=false" -e "GF_AUTH_BASIC_ENABLED=false" -e "GF_SMTP_ENABLED=true" -e "GF_SMTP_HOST=mailfwd.example.gov:25" -e "GF_SMTP_FROM_ADDRESS=levineja@example.gov" --link statsd --restart always -d grafana/grafana:2.1.3
37ff3996556b3301316a6cf8ddf7090f5ffe4c2a0bcd890561ab6814df116579
Error response from daemon: Cannot start container 37ff3996556b3301316a6cf8ddf7090f5ffe4c2a0bcd890561ab6814df116579: container already connected to network bridge

I’ve tried to remove (docker rm grafana) and rebuild the container, to no avail; there’s nothing I can figure out to do to get this container to start.

Thoughts? Do I just need to downgrade to 1.8.3 until this issue is fixed?

About this issue

  • Original URL
  • State: closed
  • Created 9 years ago
  • Comments: 31 (15 by maintainers)

Most upvoted comments

@delfuego Can you please provide your docker logs? Did this happen immediately after you upgraded to 1.9 or did you restart the daemon a few times and then run this container?

If you want to make progress the following can be used as a workaround:

  1. Stop docker daemon
  2. sudo rm /var/lib/docker/network/files/local-kv.db
  3. Start docker daemon
  4. Recreate your container

@amirkrifa as can be seen on this issue; this was a bug in 1.9.0 (which you’re running), please update docker to 1.9.1 or higher