Hey I am back here. I have been going solid for almost a year or so without any problems . I recently updated last night and rebooted and noticed the LXD service will start , but the container will not. Thinking this was a kernel issue, I rerolled back to old kernel , but after seeing that it’s still not working , I came here…
O.S Centos 7.
Linux myserver 3.10.0-862.14.4.el7.x86_64 #1 SMP Wed Sep 26 15:12:11 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
Here is the info logs on the instance that I am running called centy. https://pastebin.com/Ftm4mHwY
I thought this was a UID issue or something , but I haven’t had problems with this before.
The service is running because I can download a new image but that image will not start.
I want to say though that I like this container technology. Its for the most part solid especially since cent Os has been supported.
If not using the snap, then those two files, if they exist, must contain a valid map for the root user which covers the uid/gid ranges used by your containers, in this case, you’d need it to have access to uids
1000000 through 1001000000.
In such a scenario, quite a few things could have happened to cause this change:
Something changed the content of /etc/subuid /etc/subgid
The files didn’t exist before and something created them now, empty, blocking everything
You had those files around but didn’t have the newuidmap/newgidmap binaries
You had those binaries but they weren’t marked setuid