On a Raspberry Pi 4 I’ve OMV 5 installled.
Attached to it are 2 external disks using USB.
Docker/Portainer installed and UrBackup is installed using this great and simple guide:
In short, Add stack, name it “urbackup”, add the below docker-compose and then deploy it.
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=100 # Enter the GID of the user who should own the files here - TZ=Europe/Stockholm # Enter your timezone volumes: - /srv/dev-disk-by-label-SunSol1/urbackup/database:/var/urbackup - /srv/dev-disk-by-label-SunSol1/urbackup/backup:/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
After installing the UrBackup-client on my windows 10 machine, I noticed that the SDcard on the Pi was full. Apparently the volume-settings above did not work.
In UrBackup WebGUI, the backup path was /backup and after several trial and errors I’ve now ended up with:
…in the WEB GUI and also updated the volume setting in Portainer (and redeployed the container).
UrBackup cannot access this directory (error code 2) and I think might have to do with permissions.
I do not have any specific user for UrBackup. I’ve one OMV Webadminuser named “admin” and one “raspberry pi user” named “pi”. User “pi” has PUID 1000 & the group “pi” has PGID 100.
Since user “pi” can do anything in the system, including access the above path via ssh I’m guessing UrBackup is not using the user pi.
Could this be the case? If not, what could the issue be?