Docker networking logic - TrueNAS not reachable
Description
Steps to Reproduce
Expected Result
Actual Result
Environment
Hardware Health
Error Message (if applicable)
Activity
Bug Clerk October 10, 2024 at 12:20 PM
This issue has now been closed. Comments made after this point may not be viewed by the TrueNAS Teams. Please open a new issue if you have found a problem or need to re-engage with the TrueNAS Engineering Teams.
Bug Clerk October 10, 2024 at 9:23 AM
24.10.0 PR: https://github.com/truenas/webui/pull/10840
Bug Clerk October 9, 2024 at 2:43 PM
Connor Boyle October 8, 2024 at 10:22 PM
Hmmm, not sure why it was missing for me…
Issue originates from the PRs under NAS-131485
The subnet created by 172.17.0.0 /12 is a bit misleading as it’s usable host range still starts at 172.16.0.1, ending at 172.31.255.254.
Mister Tux October 8, 2024 at 7:50 PM
on my installation (upgraded from 24.04 to RC-1 to RC-2) the “default-address-pools” is not missing in the config file /etc/docker/daemon.json
, but I changed it from
- 172.17.0.0/12
to
- 172.17.0.0/16
Now the IP ranges are taken from 172.17.x.0/24 for newly installed apps, the existing apps are still in the range 172.16.x.0/24.
I didn’t change the “size”, is still 24 (c-class network). I guess the size was changed from RC-1 to RC-2.
After installing some Apps, the TrueNAS device is not reachable anymore from some networks. The Docker networking logic uses c-class networks 172.16.x.0/24 for each app. It doesn’t use the network where the TrueNAS itself is connected, but it uses other networks that are (eventually) in use.
The TrueNAS has an IP in the network 172.16.5.0/24, the docker networking logic does not use this network, but is using 172.16.1.0/24, 172.16.2.0/24 and so on. From this networks the TrueNAS is not reachable anymore.