$ sudo cat 50-cloud-init.yaml
# This file is generated from information provided by the datasource. Changes
# to it will not persist across an instance reboot. To disable cloud-init's
# network configuration capabilities, write a file
# /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
# network: {config: disabled}
network:
ethernets:
zz-all-en:
dhcp4: true
match: name: en* optional: true
zz-all-eth:
dhcp4: true
match: name: eth* optional: true
version: 2
Before the change cloud-init finds an IPv4 address. With the change cloud-init sees no IPv4 address. So it seems that 'optional: true' is observed now.
After login network is available with IPv4 address.
How can we ensure that at least one Ethernet port is set up?
On riscv64 preinstalled images we have
$ sudo cat 50-cloud-init.yaml cloud.cfg. d/99-disable- network- config. cfg with the following:
name: en*
optional: true
name: eth*
optional: true
# This file is generated from information provided by the datasource. Changes
# to it will not persist across an instance reboot. To disable cloud-init's
# network configuration capabilities, write a file
# /etc/cloud/
# network: {config: disabled}
network:
ethernets:
zz-all-en:
dhcp4: true
match:
zz-all-eth:
dhcp4: true
match:
version: 2
Before the change cloud-init finds an IPv4 address. With the change cloud-init sees no IPv4 address. So it seems that 'optional: true' is observed now.
After login network is available with IPv4 address.
How can we ensure that at least one Ethernet port is set up?