Ok fair enough.
Or you can still try to set up the docker container with the stack and new configuration and learn to use docker more
Ok fair enough.
Or you can still try to set up the docker container with the stack and new configuration and learn to use docker more
My app Template is suddenly lost, strangly is reverted to the state before i build the container with the app template .....
I tried your approach:
are you sure you code is valid ?
Im getting:
on line 21 - which is
Syntax Problems ?
services:
urbackup:
image: uroni/urbackup-server:latest
container_name: urbackup
restart: unless-stopped
environment:
- PUID=0 # Enter the UID of the user who should own the files here
- PGID=0 # Enter the GID of the user who should own the files here
- TZ=Europe/Berlin # Enter your timezone
volumes:
- /media/database:/var/urbackup
- /srv/dev-disk-by-label-Backups/Raid1Backups/urbackupfiles:/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
Alles anzeigen
I also looked in the Docker manual: https://docs.docker.com/compos…ose-file/compose-file-v2/
They bind the paths also, which is better ?
That /media/database has to be a shared folder, to do that you need to install the sharerootfs plugin then create a share, database, and point the path to media set the permissions, save, apply.
For instance on test OMV5 VM my docker folder is under /mnt/docker so the share is docker and the path is /mnt, so the absolute path is /mnt/docker. I hope that makes sense.
Just use a regular folder path instead of /media. I should suggest also to use a folder on your raid
@eaves im still getting yaml unmarshal error?
Whats that ?
Must the path really be a share ?
I changed it to /var/urbackupnew
i think the stack config ist not set right for the volumes or is the unmarshal error a simply cop and past error?
https://github.com/portainer/portainer/issues/2041 - the validating of staks are sadly fundamently broken - Docker seems for me very very very buggggy
Just use a regular folder path instead of /media. I should suggest also to use a folder on your raid
i bought two Wd red 4Tb which i found later out are SMR - this also describes the poor performance ....
So im not very happy to read from that Array as a DB source. The SSD is perfectly set for that
im still getting yaml unmarshal error
Never seen that error before
Must the path really be a share
Yes
do i need an absolute path
Yes
is this syntax right
It looks right, but, I think the issue is /usrbackupfiles
But, (a second but not good) I see from your post 29 you have a share Raid1Backups/ under relative path now according to;
/srv/dev-disk-by-label-Backups/Raid1Backups/database and /srv/dev-disk-by-label-Backups/Raid1Backups/urbackupfiles would tell me that the red text are sub folders of that, have you actually created those folders
This folders are on that share
Well that confirms that, the only suggestion is to do what Morlan suggested delete the container and start again but I believe it's the urbackupfiles path that's the problem. This my stack that I used to test this one has the database pointing to your first mount /media/database my original used a subfolder under the UrBackup share;
version: '2'
services:
urbackup:
image: uroni/urbackup-server:latest
container_name: urbackup
restart: unless-stopped
environment:
- PUID=998 # 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/London # Enter your timezone
volumes:
- /media/database:/var/urbackup
- /srv/dev-disk-by-label-Raid1/UrBackup:/backups
network_mode: "host"
im not sure if that's a right approach but i think i fixed it:
i removed my container and img purged all linkages:
Then i rebooted the server:
Then i installed the Docker img via the shell and gave all right path links, right away:
docker run -d --name urbackup-server-1 -v /srv/dev-disk-by-label-Backups/Raid1Backups/urbackupfiles:/backups -v /media/database:/var/urbackup -p 55413-55415:55413-55415 -p 35623:35623/udp uroni/urbackup-server
I hope that this fixed it for me
Thanks for the great support
i removed my container and img purged all linkages:
That usually solves a lot of problems, but installing from the cli is fine, if it's working that's a result
Don't worry. Containers installed from the command line will be available within Portainer for subsequent mangling.
Don't worry. Containers installed from the command line will be available within Portainer for subsequent mangling.
gresec-root does it work to connect your clients? I always had the problem that the clients never found the server when I didn’t use network_mode=host. Also you should specify a puid and pgid to avoid ownership conflicts.
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!