LXD keeps deleting the containers network device when I delete the hosts

LXD
1

So I got 2 identical machines in the cloud one of them has a public IP fine, without showing in the host. The other machine just will not do the same as the other instance.

So for the problematic machine every restart I do to it automatically creates a Veth on the host. Where as the working machine doesn’t. I have literally copy and pasted there profiles so they are the same except IP’s and yet they both behave differently.

Here is the working machines host and container.

root@routin:~# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
27: eth0@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 00:26:3e:ec:b4:9c brd ff:ff:ff:ff:ff:ff link-netnsid 0
    inet 10.1.1.153/32 scope global eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::216:3eff:feef:b49c/64 scope link
       valid_lft forever preferred_lft forever
root@routin:~# ip r
default via 10.1.1.1 dev eth0 proto static
10.1.1.0/24 dev eth0 proto kernel scope link src 10.1.1.153
root@routin:~# exitpaul@ubuntu:~$
paul@ubuntu:~$ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 02:00:25:f2:00:5b brd ff:ff:ff:ff:ff:ff
    altname enp0s3
    altname ens3
    inet 10.1.1.211/24 brd 10.1.1.255 scope global eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::15ff:fef2:5e/64 scope link
       valid_lft forever preferred_lft forever
paul@ubuntu:~$ ip r
default via 10.1.1.1 dev eth0 proto static
10.1.1.0/24 dev eth0 proto kernel scope link src 10.1.1.211
paul@ubuntu:~$

And here is the broken machine:

root@jam:~# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
root@jam:~# ip r
root@jam:~# exit
exit
22/09/22  @ 16:27 @ ~
paul@demo ——›  ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 02:00:1f:46:00:a9 brd ff:ff:ff:ff:ff:ff
    altname enp0s3
    altname ens3
    inet 10.1.1.236/24 brd 10.1.1.255 scope global eth0
       valid_lft forever preferred_lft forever
    inet 10.1.1.252/24 brd 10.1.1.255 scope global secondary eth0
       valid_lft forever preferred_lft forever
    inet 10.1.1.192/24 brd 10.1.1.255 scope global secondary eth0
       valid_lft forever preferred_lft forever
    inet 10.1.1.247/24 brd 10.1.1.255 scope global secondary eth0
       valid_lft forever preferred_lft forever
    inet 10.1.1.130/24 brd 10.1.1.255 scope global secondary eth0
       valid_lft forever preferred_lft forever
    inet 10.1.1.52/24 brd 10.1.1.255 scope global secondary eth0
       valid_lft forever preferred_lft forever
    inet6 fe30::6bff:fe2a:39/64 scope link
       valid_lft forever preferred_lft forever
22/09/22  @ 16:27 @ ~
paul@demo ——›  ip r
default via 10.1.1.1 dev eth0 proto static
10.1.1.0/24 dev eth0 proto kernel scope link src 10.1.1.236
22/09/22  @ 16:27 @ ~
paul@demo ——›

How come I can delete a interface off the host for one machine and it’s internal interface stays yet on the other it gets deleted?

2

I worked it out. I was using MacVLan in one of the configs even through everything else was set to NicType=Routed.

1 Like