BassHunger
commented
11 hours ago it is using UTC time, at that moment in summer it is always 2 hours behind
maybe the cause of not well structured yaml file? idk
quote from google search: "Do spaces matter in YAML files? YAML is whitespace-sensitive and indentation defines the structure, but it doesn't accept tabs for indentation. Empty lines are ignored. "
Hi,
I run (Version 0.0.7) on Synology NAS
My compose file:
version: '3.8' services: portainer-backup: container_name: portainer-backup-NAS03 image: savagesoftware/portainer-backup:latest hostname: portainer-backup-NAS03 restart: unless-stopped command: schedule environment: TZ: Europe/Warsaw PORTAINER_BACKUP_URL: "http://****************************:9000" PORTAINER_BACKUP_TOKEN: "****" PORTAINER_BACKUP_PASSWORD: "" PORTAINER_BACKUP_OVERWRITE: 1 PORTAINER_BACKUP_SCHEDULE: "0 0 0 *" PORTAINER_BACKUP_STACKS: 1 PORTAINER_BACKUP_DRYRUN: 0 PORTAINER_BACKUP_CONCISE: 1 PORTAINER_BACKUP_DIRECTORY: "/backup/NAS03/{{yyyy-MM-dd}}" PORTAINER_BACKUP_FILENAME: "portainer-backup-NAS03-{{yyyy-MM-dd}}.tar.gz" volumes:
If I start and have a look in log:
| _ _ | |_ _ () | _ ) _ _| | | / \ '| / ` | | ' \/ -) '| | \/ ` / | / / || | ' \ || _/| __,||||__|| |/_,_|_\,| ._/ ||
┌──────────────────────────────────────────────────────────────────┐ │ Made with ♥ by SavageSoftware, LLC © 2022 (Version 0.0.7) │ └──────────────────────────────────────────────────────────────────┘ Initializing operation : ✔ SCHEDULE Validating portainer server : ✔ http://** Validating portainer version : ✔ v2.21.1 Validating portainer access token : ✔ Validating schedule expression : ✔
[2024-09-13T11:41:04.200Z] ... Waiting for next scheduled backup
The time is 2 hour behind current Synology time (in that case it is 13:41:04).
Tried with PORTAINER_BACKUP_TZ: Europe/Warsaw - not any better.
What do I do wrong ?