AlmaLinux 9 main interface is always down on boot about distrobuilder HOT 4 CLOSED

@lukasz-zaroda are you still experiencing this issue?

I tried almalinux/9/cloud, and there is no eth0 interface. The System eth0 works as expected.

from distrobuilder.

@lukasz-zaroda are you still experiencing this issue?

Yes. Although, I no longer use Almalinux 9 as a host. I just now tested it with Ubuntu 22.04 host, and the problem persists. Please let me know if I could provide you with additional information.

This is the profile used. Image: almalinux/9/cloud.

config:
  user.network-config: |
    #cloud-config
    version: 2
    ethernets:
      eth0:
        dhcp4: no
        dhcp6: no
        addresses:
        - [MY IP ADDRESS]/32
        nameservers:
          addresses:
          - 8.8.8.8
          - 8.8.4.4
          search: []
        routes:
        - to: 0.0.0.0/0
          via: 169.254.0.1
          on-link: true
  user.user-data: |
    #cloud-config
    package_update: true
    package_upgrade: true
    packages:
      - openssh-server
description: AlmaLinux Test.
devices:
  eth0:
    host_name: veth-alma
    ipv4.address: [MY IP ADDRESS]
    nictype: routed
    parent: enp1s0f0
    type: nic
  root:
    path: /
    pool: default
    size: 3GB
    type: disk
name: almalinux-test

from distrobuilder.

I was able to reproduce your issue using the provided profile. However, I believe this has to do with the routed eth0 device as I couldn't reproduce it otherwise.

For now at least we won't change the system-generator as it solves most problems around NetworkManager in containers, and we don't want to break any other images using it.

Instead, we should allow masking units created by the lxc system-generator. Your issue can then be solved by running systemctl mask network-device-down.service and restarting the container. This only has to be done once, and there's no need to modify the cloud-config.

from distrobuilder.

Thanks, that will help! Though, it doesn't change the fact, that container of a common distro family, in common configuration is broken out of the box, which ideally should be fixed. If system-generator is too convoluted right now, to risk fixing this, then maybe some refactoring is needed, and this task simply should be postponed instead of closed? Just my 2c. Either way, the new workaround is very welcomed! :)

from distrobuilder.