[Request]: Avoid changing IP of a container unnecessary on restart
- Dominant language
- Swift
- Stars
- 49.9k
- Forks
- 1.8k
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 22
Description
### Feature or enhancement request details
Currently upon a container stop/start, the IP address will always be incremented, even if there is free IP addresses available. This can sometimes cause issues with other software running inside the container where the IPs are always changing and require reconfiguration/handling.
Even if there is a single container, start and stop will cause the container start will cause a new IP address.
### Code of Conduct
- [x] I agree to follow this project's Code of Conduct
Contributor guide
Research direction
The issue does not name files, tests, or an entry point. Start by tracing how container stop/start allocates IP addresses and how free addresses are tracked. Done means a restarted container keeps its existing IP when it remains available, including the single-container case, while allocation still works when that address is unavailable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- swift
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100