dockerd: fixed_cidr has no effect
Open
Nobody has claimed this yet.
- Dominant language
- Makefile
- Stars
- 4.6k
- Forks
- 4k
- Avg merge
- 3d 12h
- Merged PRs (30d)
- 134
Description
Maintainer: @G-M0N3Y-2503 (dockerd), @jmarcet (docker-compose)
Environment: x86, OpenWrt v23.05.05
Description:
Setting option fixed_cidr in /etc/config/dockerd has no effect. For example, setting option fixed_cidr '10.112.0.0/16' and creating a container (using docker-compose), the subnet assigned to the container's network is 172.18.0.0/16.
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
Start with the dockerd package configuration for /etc/config/dockerd and the fixed_cidr option, then reproduce by creating a container with docker-compose on OpenWrt. Trace why the configured CIDR is not used for the container network; done means 10.112.0.0/16 controls the assigned subnet instead of 172.18.0.0/16.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, docker-compose
- Domain
- infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100