"Address already in use" even if no containers connected
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 2.2k
- Forks
- 875
- PR merge metrics
- No merged PRs in 30d
Description
I regularly get the "Address already in use" error when recreating an existing container (by docker-compose), even if the container being recreated is the only member of this macVLAN network (as pointed out by docker network inspect).
Although the network shouldn't have any member left at the moment (as the container is deleted / recreated) and docker network inspect confirms this status, the underlaying IPAM database seems to have a state not matching to this output. However, I can't find a way to tell it to prune all records of addresses in use.
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
Start by reproducing container recreation with docker-compose on a macVLAN network, then compare docker network inspect with the underlying IPAM database state. The issue is complete when the stale address record no longer causes an "Address already in use" error after the container is recreated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, docker-compose, go
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100