Filesystem remapping

Incus
1

Hi, I just experienced that ownership of the root fs in one of our containers changed to nobody:nogroup. So I am trying the solution from [Container mount with user 'nobody' and group 'nogroup'].

However I am not sure about the correct mapping to try. When restarting the container I get
Error: Failed to handle idmapped storage: invalid argument - Failed to change ACLs on <path-to-rootfs>

It is also worth noting that as I copy-pasted the commands from that page I experienced Error: Failed to handle idmapped storage: Set last ID map: invalid character 'â' looking for beginning of object key string
which is just caused by the way the quotes are formatted (see https://stackoverflow.com/questions/62955553/error-chaincode-argument-error-invalid-character-%C3%A2-looking-for-beginning-of

2

While not an immediate solution to the problem at hand, it may be interesting to know what storage driver you’re running and on what kernel version.

The vast majority of Incus users are now on Linux kernels which no longer require manual idmapping.

3

Hi, thanks for your reply! The system runs a recent kernel and storage is ZFS. Does this mean that I should delete the subuid and subgid configuration?

$ uname -a
Linux hqserv 6.8.0-52-generic #53~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Wed Jan 15 19:18:46 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
$ incus --version
6.10.1
4

An update: after unsetting the volatile.last_state.idmap config item, the container started normally and the uid/gid mapping looks correct.

1 Like