码头错误: 无法启动服务... : 网络7808732465bd529e6f20e4071115218b2826f198f8cb10c3899de527c3b637e6未找到

当启动一个 docker 容器(不是我开发的)时，docker 表示还没有找到网络。

这是否意味着问题在容器本身内部(因此只有开发人员可以修复它) ，或者是否有可能改变一些网络配置来修复这个问题？

53943 次浏览
小开

I'm assuming you're using docker-compose and seeing this error. I'd recommend 

docker-compose up --force-recreate <name>

That should recreate the containers as well as supporting services such as the network in question (it will likely create a new network).

小开
最佳答案

Apparently VPN was causing this. Turning off VPN and resetting Docker to factory settings has solved the problem in two computers in our company. A third, personal computer that did not have VPN never showed the problem.

小开

I was facing this similar issue and this worked for me :

Try running this - docker container ls -a and remove the container id by docker container rm ca877071ac10 (this is the container id ).

The problem was there were some old container instances which were not removed. Once all the old terminated instances get removed, you can start the container with docker-compose file

小开

shutdown properly first, then restart

docker-compose down
docker-compose up
小开

Amongst other things docker system prune will remove 'all networks not used by at least one container' allowing them to be recreated next docker-compose up

More precisely docker network prune can also be used.

小开

This is based in this answer.

In my case the steps that produced the error where:

  1. Server restart, containers from a docker-compose stack remained stopped.
  2. Network prune ran, so the network associated with stack containers where deleted.
  3. Running docker-compose --project-name "my-project" up -d failed with the error described in this topic.

Solved simply adding force-recreate, in this way:

docker-compose --project-name "my-project" up -d --force-recreate

This possibly works because with this containers are recreated linked with the also recreated network (previously pruned as described in the pre conditions).

小开

This can be caused by some old service that has not been killed, first add --remove-orphans flag when bringing down your container to remove any undead services running, then bring the container back up

docker-compose down --remove-orphans


docker-compose up

提交答案