gaylord_fartmaster , 30 days ago

The issue is that the docker container will still be running as the LXC’s root user even if you specify another user to run as in the docker compose file or run command, and if root doesn’t have access to the dir the container will always fail.

The solution to this is to remap the unprivileged LXC’s root user to a user on the Proxmox host that has access to the dir using the LXC’s config file, mount the container’s filesystem using pct mount, and then chown everything in the container owned by the default root mapped user (100000).

These are the commands I use for this:

<span style="color:#323232;">find /var/lib/lxc/xxx/rootfs -user 100000 -type f -exec chown username {} +;
</span><span style="color:#323232;">find /var/lib/lxc/xxx/rootfs -user 100000 -type d -exec chown username {} +;
</span><span style="color:#323232;">find /var/lib/lxc/xxx/rootfs -user 100000 -type l -exec chown -h username {} +;
</span><span style="color:#323232;">find /var/lib/lxc/xxx/rootfs -group 100000 -type f -exec chown :username {} +;
</span><span style="color:#323232;">find /var/lib/lxc/xxx/rootfs -group 100000 -type d -exec chown :username {} +;
</span><span style="color:#323232;">find /var/lib/lxc/xxx/rootfs -group 100000 -type l -exec chown -h :username {} +
</span>

(Replace xxx with the LXC number and username with the host user/UID)

If group permissions are involved you’ll also have to map those groups in the LXC config, create them in the LXC with the corresponding GIDs, add them as supplementary groups to the root user in the LXC, and then add them to the docker compose yaml using group_add.

It’s super confusing and annoying but this is the workflow I’m using now to avoid having to have any resources tied up in VMs unnecessarily.