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?

  • PeepsPepperton
    link
    fedilink
    English
    arrow-up
    3
    ·
    9 months ago

    Hey, I want to say its a bit off topic, but check out Jim’s garage on YouTube regarding lxc nas folders, unprividged lxc setup. https://www.youtube.com/watch?v=DMPetY4mX-c

    You may be trying to setup the folder in unprivileged lxc, which means you need to bind in your <containerid>.conf file under /etc/pve/lxc folder on the host(proxmox}

    I hope this helps you.

    • moddy@feddit.deOP
      link
      fedilink
      English
      arrow-up
      1
      ·
      edit-2
      9 months ago

      Yes, it is unprivileged. But the mp0 is defined in the 107.conf (107 is the containerID).

      1. conf

      arch: amd64

      cores: 2

      features: keyctl=1, nesting=1

      hostname: dockge

      memory: 2048

      mpO: /media/8TB HDD

      net0: name=eth0, bridge=vmbr0, hwaddr=06: FB: 9B: 82: 17 : 58 , ip=dhcp, type=veth

      onboot: 1

      ostype: debian

      rootfs: m2 ssd 4TB:vm—107—disk—0, size=18G

      swap: 512

      tags: proxmox—helper—scripts

      unprivileged: 1

      unused0: local—1vm:vm—107—disk—0

      Is this not enough?

      I will watch the video, maybe this will help. Thanks

  • krolden
    link
    fedilink
    English
    arrow-up
    1
    ·
    9 months ago

    You should not be running docker in an lxc. This is happening because the docker container is trying to change ownership on the lxc bind mount and it is being blocked because it is not a privliged container.

    If you need to use docker, run it in a VM. You can mount your storage over NFS to the host. Or just run your backup solution in the lxc without docker.

  • theRealBassist@lemmy.world
    link
    fedilink
    English
    arrow-up
    1
    ·
    9 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.