Can lxc-to-lxd handle overlays?

LXD
1

It looks like perhaps not ?

ubuntu@u20sv6:~/Downloads$ sudo lxd.lxc-to-lxd --lxcpath /var/lib/lxc --containers afns1 --debug --dry-run
Parsing LXC configuration
Container configuration:
lxc.arch = amd64
lxc.net.0.type = veth
lxc.net.0.flags = up
lxc.net.0.link = sw1a
lxc.net.0.name = eth0
lxc.net.0.mtu = 1500
lxc.net.0.hwaddr = 00:16:3e:d3:d6:9c
lxc.net.1.type = veth
lxc.net.1.flags = up
lxc.net.0.link = sx1a
lxc.net.1.name = eth1
lxc.net.1.mtu = 1500
lxc.net.1.hwaddr = 00:16:3e:5f:cc:a0
lxc.rootfs.path = overlay:/var/lib/lxc/afns1-base/rootfs:/var/lib/lxc/afns1/delta0
lxc.uts.name = afns1
Checking for unsupported LXC configuration keys
Checking for existing containers
Checking whether container has already been migrated
Validating whether incomplete AppArmor support is enabled
Validating whether mounting a minimal /dev is enabled
Validating container rootfs
Skipping container ‘afns1’: Couldn’t find the container rootfs ‘/var/lib/lxc/afns1-base/rootfs:/var/lib/lxc/afns1/delta0’

2

No, it doesn’t. This would require a whole bunch of logic in the tool itself to re-assemble the overlay.

3

Thanks. Is there a way to convert an overlay container and it’s base container back into a single non-overlay container using lxc-copy or lxc-clone etc ?

Actually, scratch that question about condensing an overlay and it’s base back into a single container. I think I can work around that limitation.