Both instances were created by the same script, runs on the same host and have public IPs, the only difference is 7 – 11.
The problem is that I do not have internet access from the instance with IP …7 - ping google.com gives Temporary failure in name resolution.
The instance …11 is OK
Instance …11 is newly created.
Instance …7 was earlier created and deleted on another host, but inside the same net (and behind the same router).
I also created …8 and …12, where …12 is newly created and …8 is exactly the same as …7.
And with the same result - …12 is OK, …8 have no access.
Is there some kind of cache behind this story, or something else??
Curious - why are your containers using a “/32” netmask? Also, why is your default route through 169.254.0.1? Seems like you may have a typo in your profile. Compare this output with a known working container. Pay attention specifically to the netmask value.
root@hvvv7:~# resolvectl status eth0
Link 27 (eth0)
Current Scopes: none
DefaultRoute setting: no
LLMNR setting: yes
MulticastDNS setting: no
DNSOverTLS setting: no
DNSSEC setting: no
DNSSEC supported: no
Good container
root@h802459511:~# resolvectl status eth0
Link 31 (eth0)
Current Scopes: DNS
DefaultRoute setting: yes
LLMNR setting: yes
MulticastDNS setting: no
DNSOverTLS setting: no
DNSSEC setting: no
DNSSEC supported: no
Current DNS Server: 8.8.8.8
DNS Servers: 127.0.0.1
8.8.8.8
Ahhhhha
How can it be if i created both containers using the same script?
But I need to delete some containers from time to time, with the ability to re-create them in the future.
And now I see that recreated container always has empty /etc/netplan.
The big problem for me
I tried dozens of sequences of create/delete/recreate/… today, in different combinations, on the same host as yesterday, and on 2 other hosts.
Today it works as it should!
Have no idea why it didn’t want to work the last 2 days.
The host wasn’t rebooted nor upgraded for many days, but today there are no errors(?)
So I’ll add some kind of diagnostics for possible situations like these (which I should do anyway), and let’s consider the issue resolved for now(?)