issue setting up backups (new to this stuff)

Hello, I'm pretty new to this, but I have a basic understanding of what's going on. I have a server using OMV that has docker installed on it. I can access docker through Portainer.io. I set up the bedrock server using stacks. The server is running fine, but the world doesn't save when I restart the stack. I was hoping that the backups would solve this issue. I've tried to map everything correctly, but I'm not sure what I am doing wrong. This is the message I am getting in the container logs for the backups container:

time="2021-09-12T18:09:41-06:00" level=debug msg="Using /backups to match uid and gid"
time="2021-09-12T18:09:41-06:00" level=debug msg="Resolved 0 from environment variable UID"
time="2021-09-12T18:09:41-06:00" level=debug msg="Resolved 100 from environment variable GID"
The operation could not be completed. No such file or directory

This is the stack:

---
version: "2"

services:
minecraftbedrock-server:
image: itzg/minecraft-bedrock-server
container_name: minecraftbedrock-server
network_mode: host
environment:
- PUID=998
- PGID=100
- EULA=TRUE
- VERSION=1.17.11.01
- MEMORY=15G
- SERVER_NAME:Stenzilone
- ONLINE_MODE=false
- LEVEL_NAME=NoMamesWay
- ALLOW_CHEATS=true
- OPS=2535469741104124
- LEVEL_SEED=1595425848
ports:
- 19132:19132/udp
volumes:
- /srv/dev-disk-by-label-DigitalStorage01/MinecraftBedrock:/data
stdin_open: true
restart: unless-stopped

backup:
image: kaiede/minecraft-bedrock-backup
container_name: MinecraftBackup
restart: always
depends_on:
- "minecraftbedrock-server"
environment:
UID: 0
GID: 100
BACKUP_INTERVAL: "1h"
TZ: "America/Denver"
volumes:
- /var/run/docker.sock:/var/run/docker.sock
- /srv/dev-disk-by-label-DigitalStorage01/MinecraftBedrock:/minecraftbedrock-server
- /srv/dev-disk-by-label-DigitalStorage01/MinecraftBackups/backups:/backups
- /srv/dev-disk-by-label-DigitalStorage01/MinecraftBackups/config.json
stdin_open: true

I'm not sure if the UID and GID are correct

Thanks for your help!

Start with the posted Docker stack and the backup container logs, checking the three volume mappings and the UID/GID environment values. Compare the server data mount with the backup container's expected paths. Done means the backup container starts without the “No such file or directory” error and the world remains available after restarting the stack.

Written by the indexing model from the issue text.