Backups failed to start on schedule.

[david-hollingworth]

Hi

I have installed Zerobytes in a Docker container running under Portainer. I was able to create volumes and repositories no problem and scheduled two backups to run in the early hours of this morning (one at 03:00 and one at 05:00). My server is in the same TZ as I am.

However the backups did not run on schedule. I was able to manually run them and they completed fine, but for some reason the schedule didn't trigger the backups.

I checked the container logs and the only information there was related to the successful backups I'd triggered manually.

Does cron need to be enabled in the container? Did I miss something in the configuration?

This is my docker compose set up:

services: zerobyte: image: ghcr.io/nicotsx/zerobyte:v0.18 container_name: zerobyte restart: unless-stopped cap_add: - SYS_ADMIN ports: - "4096:4096" devices: - /dev/fuse:/dev/fuse environment: - TZ=Europe/Paris volumes: - /etc/localtime:/etc/localtime:ro - /var/lib/zerobyte:/var/lib/zerobyte - .config/rclone:/root/.config/rclone - nextcloud:/nextcloud - .local/share/trilium-data/backup:/trilium-backup

(full pathnames have been redacted).

Any assistance greatly appreciated.

Best regards David