RealOrangeOne / RealOrangeOne/docker-db-auto-backup
Timezone for SCHEDULE
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 201
- Forks
- 27
- PR merge metrics
- No merged PRs in 30d
Description
I've been playing with this excellent tool and it appears that the SCHEDULE environment variable always uses UTC time instead of my current timezone. I've tried various incarnations of setting the time through the volume /etc/localtime:/etc/localtime:ro and environment variable TZ=America/Los_Angeles (including both at the same time) but have not had success unless I set it to 8 hours ahead (since I'm in UTC -8). Am I missing something or does it only work in UTC time? Here is my docker compose (with both settings for time enabled):
services:
backup:
image: ghcr.io/realorangeone/db-auto-backup:latest
restart: unless-stopped
volumes:
- /var/run/docker.sock:/var/run/docker.sock:ro
- ./backups:/var/backups
- /etc/localtime:/etc/localtime:ro
environment:
- SCHEDULE=48 14 * * *
- TZ=America/Los_Angeles
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the reported Docker Compose configuration with SCHEDULE, TZ, and the /etc/localtime mount, then trace how SCHEDULE is interpreted. Done means confirming whether schedules honor the configured timezone and correcting that behavior or documenting the UTC-only behavior clearly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, python
- Domain
- databases, devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100