A couple weeks ago I posted about my attempt to upgrade a laptop running Ubuntu 20.04 with a working LXD to Ubuntu 22.04 and LXD.
Painfully, I ended doing a complete reinstall of that system in order to get LXD to where Launching a 22.04 container would actually start the container up.
Now I have a much larger Ubuntu 20.04 Desktop that I upgraded to Ubuntu 22.04 and again LXD is not working correctly.
Below you can see:
- launching a LXC “xenial” Container(CN1) does start the container but it gets NO IP4 address.
- launching a LXC “jammy” Container (CN2) … the Container gets created but does not start!
- launching a LXC “alpine” Container (CN3) creates and starts the container correctly?
$ sudo lxd init
Would you like to use LXD clustering? (yes/no) [default=no]:
Do you want to configure a new storage pool? (yes/no) [default=yes]:
Name of the new storage pool [default=default]:
Name of the storage backend to use (dir, lvm, zfs, ceph, btrfs) [default=zfs]: btrfs
Create a new BTRFS pool? (yes/no) [default=yes]:
Would you like to use an existing empty block device (e.g. a disk or partition)? (yes/no) [default=no]: yes
Path to the existing block device: /dev/sdc1
Would you like to connect to a MAAS server? (yes/no) [default=no]:
Would you like to create a new local network bridge? (yes/no) [default=yes]:
What should the new bridge be called? [default=lxdbr0]:
What IPv4 address should be used? (CIDR subnet notation, “auto” or “none”) [default=auto]:
What IPv6 address should be used? (CIDR subnet notation, “auto” or “none”) [default=auto]:
Would you like the LXD server to be available over the network? (yes/no) [default=no]:
Would you like stale cached images to be updated automatically? (yes/no) [default=yes]:
Would you like a YAML “lxd init” preseed to be printed? (yes/no) [default=no]:
$ lxc ls
±-----±------±-----±-----±-----±----------+
| NAME | STATE | IPV4 | IPV6 | TYPE | SNAPSHOTS |
±-----±------±-----±-----±-----±----------+
$ lxc launch ubuntu:xenial cn1
Creating cn1
Starting cn1
$ lxc ls
±-----±--------±-----±----------------------------------------------±----------±----------+
| NAME | STATE | IPV4 | IPV6 | TYPE | SNAPSHOTS |
±-----±--------±-----±----------------------------------------------±----------±----------+
| cn1 | RUNNING | | fd42:30d8:8bed:c58f:216:3eff:fe6f:d413 (eth0) | CONTAINER | 0 |
±-----±--------±-----±----------------------------------------------±----------±----------+
$ lxc launch ubuntu:jammy cn2
Creating cn2
Starting cn2
$ lxc launch images:alpine/edge cn3
Creating cn3
Starting cn3
$ lxc ls
±-----±--------±----------------------±----------------------------------------------±----------±----------+
| NAME | STATE | IPV4 | IPV6 | TYPE | SNAPSHOTS |
±-----±--------±----------------------±----------------------------------------------±----------±----------+
| cn1 | RUNNING | | fd42:30d8:8bed:c58f:216:3eff:fe6f:d413 (eth0) | CONTAINER | 0 |
±-----±--------±----------------------±----------------------------------------------±----------±----------+
| cn2 | STOPPED | | | CONTAINER | 0 |
±-----±--------±----------------------±----------------------------------------------±----------±----------+
| cn3 | RUNNING | 10.245.137.108 (eth0) | fd42:30d8:8bed:c58f:216:3eff:fe20:8838 (eth0) | CONTAINER | 0 |
±-----±--------±----------------------±----------------------------------------------±----------±----------+
So any suggestions as to what I can check to fix this somehow. I really do not want to have to reinstall this large Desktop system and restore from backup as it would take all night?
Any info needed?
- Ubuntu 22.04 LTS
- LXD v5.0.0
- 64GB ram
- 3 - 4 TB disks
- Linux 5.15.0-27-generic #28-Ubuntu SMP
Default Profile:
config: {}
description: Default LXD profile
devices:
eth0:
name: eth0
network: lxdbr0
type: nic
root:
path: /
pool: default
type: disk
name: default
used_by:
- /1.0/instances/cn1
- /1.0/instances/cn2
- /1.0/instances/cn3
Thanks for any ideas as I’m out of them myself…
Brian