Details
-
Improvement
-
Status: In Progress
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
Description
During Kafka system test execution, the IP range of the Docker subnet, 'ducknet' is allocated by Docker.
docker network inspect ducknet [ { "Name": "ducknet", "Id": "f4325c524feee777817b9cc57b91634e20de96127409c1906c2c156bfeb4beeb", "Created": "2018-09-09T11:53:40.4332613Z", "Scope": "local", "Driver": "bridge", "EnableIPv6": false, "IPAM": { "Driver": "default", "Options": {}, "Config": [ { "Subnet": "172.23.0.0/16", "Gateway": "172.23.0.1" } ] },
The default bridge (docker0) can be controlled externally through etc/docker/daemon.json, however, subnet created by ducknet is not. It might be a problem as many businesses make extensive use of the RFC1918 private address space (such as 172.16.0.0/12 : 172.16.0.0 - 172.31.255.255) for internal networks (e.g. VPN).
Proposed changes:
- Introduce a new subnet argument that can be used by ducker-ak up to specify IP range using standard CIDR, extend help message with the following:
If --subnet is specified, default Docker subnet is overriden by given IP address and netmask, using standard CIDR notation. For example: 192.168.1.5/24.
Attachments
Issue Links
- links to