Docker error: Cannot start service ...: network 7808732465bd529e6f20e4071115218b2826f198f8cb10c3899de527c3b637e6 not found
DockerNetworkingDocker Problem Overview
When starting a docker container (not developed by me), docker says a network
Does this mean the problem is within the container itself (so only the developer can fix it), or is it possible to change some network configuration to fix this?
Docker Solutions
Solution 1 - Docker
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).
Solution 2 - Docker
shutdown properly first, then restart
docker-compose down
docker-compose up
Solution 3 - Docker
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
Solution 4 - Docker
This is based in this answer.
In my case the steps that produced the error where:
- Server restart, containers from a docker-compose stack remained stopped.
- Network prune ran, so the network associated with stack containers where deleted.
- 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).
Solution 5 - Docker
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.
Solution 6 - Docker
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.
Solution 7 - Docker
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