Docker network not found after restart server
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 2.2k
- Forks
- 875
- PR merge metrics
- No merged PRs in 30d
Description
Hi,
I created a virtual network in docker:
docker network create \
-o parent=virbr2-lab \
-o com.docker.network.bridge.enable_icc=false \
--driver macvlan \
--subnet 192.168.2.0/24 \
--gateway 192.168.2.10 \
docker-lab2
and i connected a container (linuxserver/ubooquity) to this network and it's work but after a restart if i start the container i have this message:
docker container start ubooquity
Error response from daemon: failed to create endpoint ubooquity on network docker-lab2: network id "05669dcbecbb4298cca6f59517b6adad1a66081a7c28658213a37dc710392650" not found
Error: failed to start containers: ubooquity
but the network existe...
thanks for your help
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the reported docker network create command, container connection, server restart, and subsequent start failure. Start by inspecting how the Docker daemon restores macvlan networks and container endpoints after restart. Done means identifying why the existing docker-lab2 network ID is unavailable and adding a verified fix or regression test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100