Add note on avoiding conflicting subnets for EDA VM#32
Add note on avoiding conflicting subnets for EDA VM#32pratdesai91 wants to merge 1 commit intonokia-eda:release-25.12from
Conversation
Added a note to avoid using specific subnets that conflict with Docker.
| - 10.96.0.0/12 | ||
| - fd31:e17c:f07f:2dc0:4e2b:2ebc:cbc0:0/108 | ||
| ``` | ||
| **Note:- Avoid using 172.16-19.X.X subnets as they conflict with hypervisor Docker subnets causing cluster bootstrappign issues.** |
There was a problem hiding this comment.
Hi @pratdesai91
where did you observe the issues? Did you try to install this on a Talos or something else?
I am asking because there is no Docker on Talos setups
There was a problem hiding this comment.
Hello @hellt
These use cases are only applicable when the hypervisor itself also hosts the edaadm package server.
In most customer environments, there is no separate jump‑box provided for running the image‑processing or configuration‑rendering steps. Because of that limitation, I typically install Docker directly on Hypervisor‑1 to run the kpt‑setter workflow required for an air‑gapped EDA installation.
This ensures that all rendering, packaging, and artifact preparation can be completed locally on the hypervisor, even when external registry access or an intermediate workstation is not available.
2 participants
Added a note to avoid using specific subnets that conflict with Docker.