Hi All,
We’ve had a problem when we moved a container from one host in a cluster to another, when starting the container on the new host in the cluster it says “Mapping container” which was unexpected, checking the nfs shares yielded nobody:nogroup.
Checking more the settings changed from:
volatile.idmap.current: ‘[{“Isuid”:true,“Isgid”:false,“Hostid”:100000,“Nsid”:0,“Maprange”:65536},{“Isuid”:false,“Isgid”:true,“Hostid”:100000,“Nsid”:0,“Maprange”:65536}]’
to:
volatile.idmap.next: ‘[{“Isuid”:true,“Isgid”:false,“Hostid”:1000000,“Nsid”:0,“Maprange”:1000000000},{“Isuid”:false,“Isgid”:true,“Hostid”:1000000,“Nsid”:0,“Maprange”:1000000000}]’
Why was it changed, we had to do the following, shut down the container then ran:
/snap/bin/lxc config set container volatile.idmap.next=’[{“Isuid”:true,“Isgid”:false,“Hostid”:100000,“Nsid”:0,“Maprange”:65536},{“Isuid”:false,“Isgid”:true,“Hostid”:100000,“Nsid”:0,“Maprange”:65536}]’
Started it, and then nfs uid+gid was good.
Just curious and trying to understand why it behaves this way? Surely it should copy the existing container config across to the new vm?
Cheers
Jonathan