Compose won't start container: already connected to network #17729
Comments
|
Hi! Please read this important information about creating issues. If you are reporting a new issue, make sure that we do not have any duplicates already open. You can ensure this by searching the issue list for this repository. If there is a duplicate, please close your issue and add a comment to the existing issue instead. If you suspect your issue is a bug, please edit your issue description to include the BUG REPORT INFORMATION shown below. If you fail to provide this information within 7 days, we cannot debug your issue and will close it. We will, however, reopen it if you later provide the information. This is an automated, informational response. Thank you. For more information about reporting issues, see https://github.com/docker/docker/blob/master/CONTRIBUTING.md#reporting-other-issues BUG REPORT INFORMATIONUse the commands below to provide key information from your environment:
Provide additional environment details (AWS, VirtualBox, physical, etc.): List the steps to reproduce the issue: Describe the results you received: Describe the results you expected: Provide additional info you think is important: ----------END REPORT --------- #ENEEDMOREINFO |
|
Similar issue for me upgrading to 1.9 on Ubuntu 14.04. Rebooting host OS, and then running a new container solved it for me. |
|
I got same problem. I downgraded back to 1.8.3 and problem went away. Later i realised that compose was still in version 1.4.0. i'll try to upgrade compose 1.5.0 and try again later. |
|
Same issue on Mac OS 10.11.1 and Docker version 1.9.0, build 76d6bc9 |
|
FYI: Glad to see I am not the only one with this problem. |
|
Possibly a duplicate or at least related to #17621 |
|
@dnephin Except my container is not connected to any network. I checked my other two network (none, host) container lists, both empty. Or am I not understanding libnetwork? |
|
Are you able to inspect the container, either by container_name or id? The output of a |
|
Output of docker inspect: |
|
If you |
|
+1 |
|
+1 |
|
If you run |
|
@joskuijpers Can you please provide the complete docker log? Did this container exist from before? I see a lot of GETs for the container. |
|
I can't reproduce. I've tried with a compose file with 6 services I've done multiple combinations of I also created a 1.8.3 machine, started and stopped my containers with compose and upgraded using Docker Machine to 1.9. Then I performed the same steps above and was still unable to reproduce. It would be helpful to understand how you upgraded:
If you are using machine, it might be worthwhile creating a fresh one to see if you can reproduce: |
|
|
|
I've encountered what appears to be same issue after upgrading Docker on Debian 8.0 via apt-get. |
|
|
|
Fixed this problem by first removing the troublesome container by name and then by id: |
|
I upgraded using the toolbox. I just downloaded the new 1.9 toolbox and ran it. It told me it would upgrade to 1.9. I did compose stop, then composte --project-name xxx up -d: So it seems it does indeed exist. docker ps -a contains all my containers. (old project, new project). Old project is exited, new project is running, except nginx, which is just created. Only containers in my network are the actually running ones. Yeah, so when creating that composetest machine, I got asked for a password, but then I got an error. Now my console is locked in password-input mode... lets try again. Now I get asked for a password (randomly in my console), I have no clue what password... 😭 |
|
@dave-tucker It might help to add some links between te containers? I stripped my compose file, and ran it with a fresh project name nginx:
restart: always
image: nginx
ports:
- "80:80"
- "443:443"
links:
- "node:node"
node:
image: node
links:
- redis
- pgbnc
- graphite
expose:
- "8080"
ports:
- "35729:35729"
- "5858:5858"
pgbnc:
image: starefossen/pgbouncer
links:
- db
ports:
- "5432:5432"
db:
image: postgres
environment:
POSTGRES_PASSWORD: XXXX
expose:
- "5432"
redis:
image: redis
ports:
- "6379:6379"
graphite:
image: hopsoft/graphite-statsd
ports:
- "8080:80"
expose:
- "2003:2003"
- "8125:8125/udp"I tested this one (so I kept all the ports. You might want to remove some or many). Same as above. And same story, I don't see any container in my network that may cause this. I wanted to restart my VBox using docker-machine, but after running docker-machine ls, I got stuck in the password input again (the application already closed, as in, my console input line is visible). |
|
|
|
So I tried the docker-machine upgrade, I am crying. What is going on? Did the Docker Toolbox just screw up my whole setup? Is machine damaged on my machine? |
|
@joskuijpers looks like there is something wrong with your machine install I'm running this version: You might want to try with debug enabled You could always re-install with the one liner from here Will re-try with your compose file and see if I can reproduce |
|
same issue here. Any suggestion for who is not using docker-machine? |
icecrime
added
priority/P1
|
I encountered the same thing updating a toolbox 1.8.3 install to 1.9. I first tried wiggling it a little by modifying the compose config for the failing container, changing its name, links, etc, but nothing. A For what its worth, before this I hit docker/machine#2175 after the update running the quickstart terminal, iirc, and went ahead with |
|
I've seen this also on CentOS sporadically, maybe related, to #17653? |
|
After a restart of my mac, the problems with docker-machine are resolved (I had to generate new certs for my composetest, like docker/machine#2175). Running compose on the new VBox works, no connection errors. I stopped compose test, started my original machine, and it created the nginx container just fine now. Everything I have done is written down in this issue. I am sorry I can't be of more help. |
|
Resolved by #17558. |
|
For anyone who's still having this issue for me the resolution was (on Ubuntu 15.10, docker 1.9.0, compose 1.5.1): and then it worked again. |
|
@milosonator temporary fix worked for me as well. |
|
Had same issue as well. docker-machine upgrade fixed it. |
|
@milosonator I tried your |
and others
Today I upgraded to 1.9 on my OSX machine.
docker version:
docker info:
uname -a:
I tried to start my unchanged development environment using
docker-compose up -d, and this was the result:The failing container is nginx.
I expected the nginx containter to start successfully.
Running
docker network inspect bridgeafter the previous command:I can't find the 'already connected' container.
Debug logs:
If any more information is required, please tell. I can put some time in trying to create a minimal example, or starting compose from another folder to create all new containers. The current compose file would be useless as you don't have all my dockerfiles and related files.
The text was updated successfully, but these errors were encountered: