Hi,
about a week ago I started getting my NUC-Server working because of problems with my nextcloud container (Docker on Synology).
Especially with the data folder for nextcloud I had / have my problems. This folder shall not be locally on my NUC. Until a problem while the installation (Tried with snap but externl DB was not working) I decided to do a restore before the snap installation. From this point on I mentioned that the mount point was no longer writable.
As a container is not so much work to setup I started from scratch with this one. So far so good but I'm not able to get the MountPoint and lxc.idmap back to work.
So please I need some help and hope someone here is able to see my mistake.
Synolgy NAS:
User: 1044:100
PVE:
Storage as CIFS with Synology user credentials adde by gui and Disk image content.
User root is able to write/delete below the mounted folder.
The result does not change after "chown -R 1044:1000 /mnt/pve/nextcloud" with Synology UID. There is no additional local user created.
LXC from Debian 11 template (101):
Nested=1
unpriliged=1
Updated timezone and NTP.
Added new user with sudo capability.
Updated / Upgraded the container .
Changed the UID from 1000 to 1044. Group ID was not changed.
Created mount folder /mnt/data and chown -R 1044:1000.
Later www-data (nextcloud needs this) should get the UID 1044, so the above user change is for test only.
Stopped the CT.
PVE:
Executed:
Added the following to the /etc/pve/lxc/101.conf
Added the following to the /etc/subuid and /etc/subguid
I tried also to change the group ID of the LXC user and added also a user with the same credentials on the PVE. Both without luck. The user add created also some additional entris within subuid and subguid. Maybe I misunderstand somethind with the lxc.idmap. I'm not realy sure wich column stands for PVE or LXC.
When I start the container within the PVE Terminal there are two Errors:
"systemd-journald-audit.socket: Failed to create listening socket (audit 1): Operation not permitted" and
"Failed to mount Kernel Configuration File System"
On stop:
"[FAILED] Failed unmounting /mnt/data."
Maybe more details within the attached log
The second and the failure on stop maybe cause the problem but I don#t know what to do. My search result was not so helpfull for me.
Mainly I found a quite similar post but I don't see what I do wrong. Also the wiki didn't helped me.
I also tried so much different combinations without result. Thats bit frustrating and makes me realy lost. Especially as it was working and I don't know what I've done different before. So please help I don't know what I can do anymore.
Best regards
Indy
about a week ago I started getting my NUC-Server working because of problems with my nextcloud container (Docker on Synology).
Especially with the data folder for nextcloud I had / have my problems. This folder shall not be locally on my NUC. Until a problem while the installation (Tried with snap but externl DB was not working) I decided to do a restore before the snap installation. From this point on I mentioned that the mount point was no longer writable.
As a container is not so much work to setup I started from scratch with this one. So far so good but I'm not able to get the MountPoint and lxc.idmap back to work.
So please I need some help and hope someone here is able to see my mistake.
Synolgy NAS:
User: 1044:100
PVE:
Storage as CIFS with Synology user credentials adde by gui and Disk image content.
User root is able to write/delete below the mounted folder.
Code:
ls -ld /mnt/pve/nextcloud/
drwxr-xr-x 2 root root 0 Sep 20 10:26 /mnt/pve/nextcloud/LXC from Debian 11 template (101):
Nested=1
unpriliged=1
Updated timezone and NTP.
Added new user with sudo capability.
Updated / Upgraded the container .
Changed the UID from 1000 to 1044. Group ID was not changed.
Created mount folder /mnt/data and chown -R 1044:1000.
Later www-data (nextcloud needs this) should get the UID 1044, so the above user change is for test only.
Stopped the CT.
PVE:
Executed:
Code:
pct set 101 -mp0 /mnt/pve/nextcloud,mp=/mnt/data
Code:
lxc.idmap%3A u 0 100000 1044
lxc.idmap: g 0 100000 1000
lxc.idmap: u 1044 1044 1
lxc.idmap: g 1000 1000 1
lxc.idmap: u 1045 101045 64491
lxc.idmap: g 1001 101001 64535
Code:
root:1044:1I tried also to change the group ID of the LXC user and added also a user with the same credentials on the PVE. Both without luck. The user add created also some additional entris within subuid and subguid. Maybe I misunderstand somethind with the lxc.idmap. I'm not realy sure wich column stands for PVE or LXC.
When I start the container within the PVE Terminal there are two Errors:
"systemd-journald-audit.socket: Failed to create listening socket (audit 1): Operation not permitted" and
"Failed to mount Kernel Configuration File System"
On stop:
"[FAILED] Failed unmounting /mnt/data."
Maybe more details within the attached log
The second and the failure on stop maybe cause the problem but I don#t know what to do. My search result was not so helpfull for me.
Mainly I found a quite similar post but I don't see what I do wrong. Also the wiki didn't helped me.
I also tried so much different combinations without result. Thats bit frustrating and makes me realy lost. Especially as it was working and I don't know what I've done different before. So please help I don't know what I can do anymore.
Best regards
Indy