What you're doing with raw.lxc can be done using raw.idmap instead which
would have saved you from the upgrade problem.
The upgrade issue is because liblxc now expects it to be lxc.idmap
rather than lxc.id_map.
https://github.com/lxc/lxd/blob/master/doc/userns-idmap.md
--
You received this bug
Ah, I see. So is raw.lxc completely unsupported, or is it only the
upgrade that is unsupported? If the latter, no problem, I can trash and
recreate the containers. Or is there some better way of achieving what
I'm doing?
I'm using lxc for testing i386 target from my x86-64 host without having
to d
Marking the bug as invalid since it's caused by unsupported user
configuration.
Please comment here if you find yourself unable to correct this somehow.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1
The DPKG error is reasonably clear:
- xenial9: Failed to load raw.lxc
That indicates you have a container (or more) that have a raw.lxc
configuration key which is incompatible with the newer version of LXC
that's in 3.0.
You should unset this key and then run the upgrade again.
"raw.lxc" is an
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1784846
Title:
package lxd 3.0.1-0ubuntu1~18.04.1 failed to install/upgrade:
installed lxd package post-installa
