7
submitted 8 months ago* (last edited 8 months ago) by moddy@feddit.de to c/selfhosted@lemmy.world

Love Proxmox but still have to learn a lot... I use a Bind Mount Point for my dockge-LXC on proxmox.

I used the Mount Point in my docker compose:

version: "2"

services: urbackup:

image: uroni/urbackup-server:latest

container_name: urbackup

restart: unless-stopped

environment:

  - PUID=1000 # Enter the UID of the user who should own the files here

  - PGID=1000 # Enter the GID of the user who should own the files here

  - TZ=Europe/Berlin # Enter your timezone

volumes:

  - /media/urbackups/data:/var/urbackup

  - /media/urbackups/storage:/backups

  # Uncomment the next line if you want to bind-mount the www-folder

  #- /path/to/wwwfolder:/usr/share/urbackup

network_mode: host

# Activate the following two lines for BTRFS support

cap_add:

  - SYS_ADMIN

networks: {}

Now i geht this permission-error:

urbackup | usermod: no changes

urbackup | chown: changing ownership of '/backups': Operation not permitted

I guess it has to do with the PUID, but i do not know the PUID.

I read that it has to be the user "urbackup" but also in the docker?

The mounted folders are both 777.

Can you help me?

you are viewing a single comment's thread
view the rest of the comments
[-] theRealBassist@lemmy.world 1 points 8 months ago

There's a weird thing with bind mounts and permissions.

In my case, for my Ubuntu VM to have correct perms for 0:0 (root), the PID and GID in ProxMox's fstab need to be like 11000:10000 or something.

It's apparently working as intended that way, but it's weird.

this post was submitted on 04 Mar 2024
7 points (88.9% liked)

Selfhosted

40113 readers
331 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS