Tom Parrott
Tom Parrott
Please show "lxc config show (instance) --expanded" before and after restore.
Reproduced the issue.
This will be because the storage volume's idmap settings (when not using idmapped mounts from the kernel) are stored in the storage volume's DB record, e.g. ``` lxc storage volume...
Idmapped mounts for the win!
@roosterfish please close this one as part of your lxd recover improvements pr ta
> > > [01e9f17](https://github.com/canonical/lxd/commit/01e9f17e8ace5cb3dc007ae82c310bcc19836cbb) > > > > > > I intentionally squashed these since they were "tiny" follow up commits. One is a formatting and readability change ([lxc/incus@51a07ac](https://github.com/lxc/incus/commit/51a07ac38ef1bf0625fd1b14907c92ac05da7f24)), and...
please rebase
@kadinsayani why did you not pick all from https://github.com/lxc/incus/pull/1019 ?
Provide `armhf` `lxd-agent` in `arm64` snap to enable `lxc exec` into 32 bit guests from 64 bit host
https://github.com/lxc/incus/pull/427 might help with this
Yes this does raise some interesting scenarios, like what if the device type is different in the instance than the device being overridden from the profile. Lets hold off on...