I've been working with Red Hat's CodeReady Containers and I recently had a networking issue that might not be obvious to all users.
Hyper-V assigns your VM to an address space in the 172.x.x.x range.
CRC also assigns, by default, in the 172.30.0.0/16 address space.
This all works well unless Windows assigns your VM an address in 172.30.x.x as well. Then you get a bunch of networking issues where you can't connect outside the cluster. This means you can't download images, etc.
The solution - reboot your PC and restart CRC until you get an address outside the 172.30.x.x range.
Comments
Post a Comment