[Netplan config breaks podman, docker, VM networking by trying to manage virtual bridge network interfaces]

As configured on install (at least in 24.8.4 I installed), the netplan config files try to manage all networking interfaces - which breaks the virtual bridge interfaces that containers and VM managers like Podman, Docket, etc create and use.

 

See https://github.com/moby/moby/issues/40217#issuecomment-2041628162 for more information

 

If networkctl shows podman* or veth* as managed then this is probably the problem breaking your container networking.

 

To work around this issue, I modified the file /etc/netplan/10-dhcp-all-interfaces.yaml to only manage en* interfaces rather than all interfaces, followed by netplan apply.

 

# Added by Armbian
#
# Reference: https://netplan.readthedocs.io/en/stable/netplan-yaml/
#
# Let systemd-networkd manage all Ethernet devices on this system, but be configured by Netplan.

network:
  version: 2
  renderer: networkd
  ethernets:
    all-eth-interfaces:
      match:
        name: "en*"
      dhcp4: yes
      dhcp6: yes
      ipv6-privacy: yes # Enabled by default on most current systems, but networkd currently doesn't enable IPv6 privacy by default, see https://man.archlinux.org/man/systemd.network.5
    lo-interface:
      match:
        name: lo
      dhcp4: yes
      dhcp6: yes
      ipv6-privacy: yes # Enabled by default on most current systems, but networkd currently doesn't enable IPv6 privacy by default, see https://man.archlinux.org/man/systemd.network.5

Note: netplan doesn't support globs/etc on name line yet hence the need for two ethernets entries, see https://github.com/canonical/netplan/pull/202

[Method to boot with BSP kernel to compare power usage to mainline kernel?]

Is there a method to boot with BSP kernel (the 4.4 kernel supplied by Rockchip/Radxa) on an existing install (jammy) to compare power usage to mainline kernel (5.15.y current or even 5.19.y rolling)?

 

I tried using the switch kernel support in armbian-config, but the linux-image-legacy-rockchip64 4.4.213-rockchip64 just hung during early boot and had to recover to linux-image-current-rockchip64 5.15.69 . 

 

P.S. This is related to my question on the Radxa forums about reducing Rock Pi 4 B+ power usage.