There have been multiple accounts created with the sole purpose of posting advertisement posts or replies containing unsolicited advertising.

Accounts which solely post advertisements, or persistently post them may be terminated.

Proxmox: Trouble with permissions of data in a mountpoint for a lxc (audiobookshelf)

I am moving from an debian-server (odroid) to a proxmox-server. I have a 2tb-ssd for some media in my proxmox, so that is what i did:

  1. i mounted the smaba-share from my old server in proxmox (not in the lxc “ausiobookshelf”)
  2. i moved the data from the old server to the lxc-mountpoint “audiobooks” on my proxmox

This worked but now i have trouble to give permissions. In proxmox i can edit the permissions but there is no user “audiobookshelf” in the proxmox-root. In the lxc i have the user “audiobookshelf” but i have no rights to edit the permissions.

Question: What is the best solution to move data to lxc-mountpoints regarding the permissions? Should i use a systemwide user or group? Or should i mount the samba-share from the old server in the lxc?

audiobookshelf is only the beginning. SABnzbd and jellyfin will follow so i ask in common… ;)

monty33 ,

I have had these permission issues in the past. Once I switched to mounting directly in the LXC they all went away.

lemmyng ,
@lemmyng@lemmy.ca avatar

Figure out the uid/gid (numeric) for the user in lxc, then change the data permissions to those.

moddy OP ,

Or should i solve it by chmod instead of owner/group?

jay ,
@jay@mbin.zerojay.com avatar

Proxmox maps user ids between itself and lxc containers and it took me a bit of time to figure it out. I would highly suggest reading the following link as it's how I worked it out. I ended up chown'ing to 101000 which maps to user 1000 - the default user - in my lxcs.

https://www.itsembedded.com/sysadmin/proxmox_bind_unprivileged_lxc/

tvcvt ,

I’m making some assumptions, namely that you’re using an unprivileged LXC container and the mount point is a bind mount.

Unprivileged LXC shift user ID numbers so that an escape won’t result in root access to the host. The root user (uid 0) in the container is actually uid 100000 from the perspective of the Proxmox host.

What I usually do is set ownership of my bind mounts to that high-numbered ID (so something like chown -R 100000:100000 /path/to/bind/mount) from Proxmox. Then the root user in the container will be able to set whatever permissions you need directly.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • •
  • [email protected]
  • random
  • lifeLocal
  • goranko
  • All magazines
    •