Sorry, I was a bit tired yesterday. I should have realized that in this case itâs expected that a LXD server is to be passed as parameter. Use of the same syntax for the LXD global configuration and container configuration can get a bit confusing.
lxc config show --expanded jitsistable
architecture: x86_64
config:
image.architecture: amd64
image.description: ubuntu 20.04 LTS amd64 (release) (20220104)
image.label: release
image.os: ubuntu
image.release: focal
image.serial: "20220104"
image.type: squashfs
image.version: "20.04"
volatile.base_image: 5e94999280de957497662d414bcd84766b55903c42af5bff9ea39a3cacabad12
volatile.eth0.hwaddr: 00:16:3e:41:a2:83
volatile.eth0.name: eth0
volatile.idmap.base: "0"
volatile.idmap.current: '[{"Isuid":true,"Isgid":false,"Hostid":1000000,"Nsid":0,"Maprange":1000000000},{"Isuid":false,"Isgid":true,"Hostid":1000000,"Nsid":0,"Maprange":1000000000}]'
volatile.idmap.next: '[{"Isuid":true,"Isgid":false,"Hostid":1000000,"Nsid":0,"Maprange":1000000000},{"Isuid":false,"Isgid":true,"Hostid":1000000,"Nsid":0,"Maprange":1000000000}]'
volatile.last_state.idmap: '[]'
volatile.last_state.power: STOPPED
volatile.uuid: fb876dda-7290-4101-8380-75f9b74ac98b
devices:
eth0:
nictype: macvlan
parent: eno1
type: nic
root:
path: /
pool: default
type: disk
ephemeral: false
profiles:
- default
- nonic
stateful: false
description: ""
For comparison, here is one I imported by first copying to another LXD server, and copying it back to the new OS (in this case remapping does its thing) - I post here not because I want a workaround, I can do without it because the LXD resources are enough to solve it, however I suspect I am getting into a unexpected result in a corner case.
architecture: x86_64
config:
image.architecture: amd64
image.description: ubuntu 20.04 LTS amd64 (release) (20211108)
image.label: release
image.os: ubuntu
image.release: focal
image.serial: "20211108"
image.type: squashfs
image.version: "20.04"
volatile.apply_template: copy
volatile.base_image: bd2ffb937c95633a28091e6efc42d6c7b1474ad8eea80d6ed8df800e44c6bfdd
volatile.eth0.hwaddr: 00:16:3e:17:28:d0
volatile.eth0.name: eth0
volatile.idmap.base: "0"
volatile.idmap.next: '[{"Isuid":true,"Isgid":false,"Hostid":1000000,"Nsid":0,"Maprange":1000000000},{"Isuid":false,"Isgid":true,"Hostid":1000000,"Nsid":0,"Maprange":1000000000}]'
volatile.last_state.idmap: '[{"Isuid":true,"Isgid":false,"Hostid":1000000,"Nsid":0,"Maprange":1000000000},{"Isuid":false,"Isgid":true,"Hostid":1000000,"Nsid":0,"Maprange":1000000000}]'
volatile.uuid: 2e304b47-eee0-426f-b08e-2395eb068d4c
devices:
eth0:
nictype: macvlan
parent: eno1
type: nic
root:
path: /
pool: default
type: disk
ephemeral: false
profiles:
- default
- nonic
stateful: false
description: ""
Difference seems obvious: bad container has not the âvolatile.apply_template: copyâ line. However from memory when I created the 2 containers I did not follow a different procedure (I have a script to create new containers) so it does not seem likely there were different on the original OS. I can still boot it if you think it would be helpful to make sure.