Replies: 2 comments
-
Is it possible that firewalld ships with different defaults in newer versions of the package? The v3.4.2 image that worked for you would have the package version that was in the repositories at the time of building, with whatever rules it was shipped with. |
Beta Was this translation helpful? Give feedback.
-
You should try the newer init v0.5.5 version as a few things changed for RHEL variants. We moved to use the default NetworkManager that ships with vanilla. If we find systemd-networkd in the system, we enable that instead. We set several switches to set the proper initramfs modules. And we tested rocky/alma 10 to make it work as expected with the dropped packages. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I'm trying to build own Kairos based on rockylinux. Here's my simple Dockerfile:
Building it with next commands:
Then I download http://localhost:8080/kairos-rocky-9.6-standard-amd64-generic-v0.0.4-k0sv1.33.2+k0s.0.iso and boot target node from it. It loads fine, shows Kairos logo and address for the WebUI Installer.
I can ping this IP address but the opening of 8080 port gives me timeout!
Looks like firewalld blocks incoming connections.
However if I boot from https://github.com/kairos-io/kairos/releases/download/v3.4.2/kairos-rockylinux-9-standard-amd64-generic-v3.4.2-k0sv1.32.4+k0s.0.iso I can reach WebUI Installer.
Then I tried to build same Dockerfile but from rockylinux/rockylinux:10 and it failed:
I also tried to install same set of deps and it looks like dhcp-client is not available.
Beta Was this translation helpful? Give feedback.
All reactions