IP allocation failed because task stops not cleanup?
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 3.7k
- Forks
- 676
- Avg merge
- 4d 9h
- Merged PRs (30d)
- 6
Description
created network:
docker network create --opt encrypted -d overlay --attachable frontend
after a while with starting stoping tasks and attaching (when the ip range exceeds)
no more task can attached to the network:
task allocation failure" error="failed to allocate network IP for task ep3bjhcmfkc6du1993m8sfl29 network 1j2ewqwprzwsli8tm9tzee0wu: could not find an available IP" module=node node.id=jnbv0b1ot5quu17868zbfip0k
Contributor guide
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 issue with the provided overlay network command by repeatedly starting, stopping, and attaching tasks until the IP range is exhausted. Trace task allocation and cleanup from the resulting “could not find an available IP” error; done means released task addresses become available for later tasks without allocation failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go
- Domain
- distributed-systems, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100