Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Time issue #22

Open
ilexpl01 opened this issue Sep 13, 2024 · 3 comments
Open

Time issue #22

ilexpl01 opened this issue Sep 13, 2024 · 3 comments

Comments

@ilexpl01
Copy link

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:
- /volume1/docker/portainer_backup:/backup

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 ?

@BassHunger
Copy link

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. "

@oddife
Copy link

oddife commented Oct 18, 2024

@ilexpl01 Did you find any solution for this issue

@ilexpl01
Copy link
Author

No :(

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

3 participants