From 45d5ff16e9b71f8ebfe15677f98bb1ced08f0df7 Mon Sep 17 00:00:00 2001 From: akanealw Date: Sat, 10 Aug 2024 00:54:38 -0500 Subject: [PATCH] updated --- documents/proxmox/proxmox_lxc_usermappings/content.md | 9 ++++----- 1 file changed, 4 insertions(+), 5 deletions(-) diff --git a/documents/proxmox/proxmox_lxc_usermappings/content.md b/documents/proxmox/proxmox_lxc_usermappings/content.md index 1316a64..a7c0802 100644 --- a/documents/proxmox/proxmox_lxc_usermappings/content.md +++ b/documents/proxmox/proxmox_lxc_usermappings/content.md @@ -24,19 +24,18 @@ lxc.idmap: u 1001 101001 64535 //maps 1001-65535(CT) -> 101001-165535(Host) To fix this: -1. Remove the mappings in config and restart the CT. This should revert the ownership back to akanealw. +Remove the mappings in config and restart the CT. This should revert the ownership back to akanealw. -2. Then use root/sudo to change ownership of the directory/files to root on the container +Use root/sudo to change ownership of the directory/files to root on the container ```bash sudo chown root:root -R /home/akanealw sudo chown root:root /var/spool/cron/crontabs/akanealw ``` -3. Next, shutdown the container and reapply the mappings in config. Now when you restart the container, /home/akanealw should still be owned by root. +Shutdown the container and reapply the mappings in config. Now when you restart the container, /home/akanealw should still be owned by root. -4. Lastly, using container's root and change ownership back to the newly mapped akanealw +Using container's root and change ownership back to the newly mapped akanealw ```bash sudo chown akanealw:akanealw -R /home/akanealw sudo chown akanealw:crontabs /var/spool/cron/crontabs/akanealw ``` -