After a restart of the container I can ping local IPs. resolvectl reports an “empty” config:
root@focaltest:~# resolvectl status
Global
LLMNR setting: no
MulticastDNS setting: no
DNSOverTLS setting: no
DNSSEC setting: no
DNSSEC supported: no
DNSSEC NTA: 10.in-addr.arpa
16.172.in-addr.arpa
168.192.in-addr.arpa
17.172.in-addr.arpa
18.172.in-addr.arpa
19.172.in-addr.arpa
20.172.in-addr.arpa
21.172.in-addr.arpa
22.172.in-addr.arpa
23.172.in-addr.arpa
24.172.in-addr.arpa
25.172.in-addr.arpa
26.172.in-addr.arpa
27.172.in-addr.arpa
28.172.in-addr.arpa
29.172.in-addr.arpa
30.172.in-addr.arpa
31.172.in-addr.arpa
corp
d.f.ip6.arpa
home
internal
intranet
lan
local
private
test
Link 49 (eth0)
Current Scopes: none
DefaultRoute setting: no
LLMNR setting: yes
MulticastDNS setting: no
DNSOverTLS setting: no
DNSSEC setting: no
DNSSEC supported: no
It seems that cloud init was mostly ignored as netplan get show absolutely nothing:
root@focaltest:~# netplan get
root@focaltest:~#
I’ve spawned a images:ubuntu/focal/cloud container, applied my default, my cloud_init and the mentioned routed profiles and it worked like a charm. netplan was reporting the correct config, resolvectl status too and the container was able to resolve hosts.
It seems that my problem is related to the broken cloud_init functionality on the ubuntu-minimal containers and I wonder if there’s a way to notify the maintainers of ubuntu-minimal of the problems with focal images…