Replies: 2 comments
-
I believe my issue has something to do with docker itself. I'm trying out a few things. I'll update this after my testing. |
Beta Was this translation helpful? Give feedback.
0 replies
-
You should look for the |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello, noob to Restic here!
I set up djmaze / restcker today. I'm using the docker compose .yaml file as my template. I'm deploying via Portainer stacks.
My server is running Ubuntu and has 1.8Tb of storage, my backup drive also has 1.8Tb of free storage.
When my container deploys, I can follow the logs and everything seems to run fine until the actual backup happens. Then I get some errors about no space on my backup drive. Restic is trying to back up 455.296 GiB worth of data to a 1.8Tb free, empty, fresh drive.
I'm missing something and I don't know what to search for to find helpful / useful info. I defiantly have been prowling around the internet, but I'm becoming more lost.
Why does Restic think I'm out of space?
Thanks for any help!
If you need more info please advise.
Here is my docker compose script.
`
version: "3.3"
services:
backup:
image: mazzolino/restic
hostname: ig88
restart: unless-stopped
environment:
RUN_ON_STARTUP: "true"
BACKUP_CRON: "0 */24 * * *"
RESTIC_REPOSITORY: /mnt/backuphdd/restic
RESTIC_PASSWORD: [REDACTED]
RESTIC_BACKUP_SOURCES: /mnt/mstorage
RESTIC_BACKUP_ARGS: >-
--verbose
RESTIC_FORGET_ARGS: >-
--keep-last 10
--keep-daily 7
--keep-weekly 5
--keep-monthly 12
TZ: America/Denver
volumes:
- /mnt/backuphdd/restic-backups
- /mnt/backuphdd/restic-restore
- /mnt/mstorage/:/mnt/mstorage:ro
prune:
image: mazzolino/restic
hostname: ig88
restart: unless-stopped
environment:
SKIP_INIT: "true"
RUN_ON_STARTUP: "true"
PRUNE_CRON: "0 0 4 * * *"
RESTIC_REPOSITORY: /mnt/backuphdd/restic
RESTIC_PASSWORD: [REDACTED]
TZ: America/Denver
check:
image: mazzolino/restic
hostname: ig88
restart: unless-stopped
environment:
SKIP_INIT: "true"
RUN_ON_STARTUP: "false"
CHECK_CRON: "0 15 5 * * *"
RESTIC_CHECK_ARGS: >-
--read-data-subset=10%
RESTIC_REPOSITORY: /mnt/backuphdd/restic
RESTIC_PASSWORD: [REDACTED]
TZ: America/Denver
`
Here is the log file when the container runs.
Checking configured repository '/mnt/backuphdd/restic' ... Fatal: repository does not exist: unable to open config file: stat /mnt/backuphdd/restic/config: no such file or directory Is there a repository at the following location? /mnt/backuphdd/restic Could not access the configured repository. Trying to initialize (in case it has not been initialized yet) ... created restic repository 9881404eac at /mnt/backuphdd/restic Please note that knowledge of your password is required to access the repository. Losing your password means that your data is irrecoverably lost. Repository successfully initialized. Executing backup on startup ... Starting Backup at 2025-01-20 15:05:52 open repository no parent snapshot found, will read all files load index files start scan on [/mnt/mstorage] start backup on [/mnt/mstorage] scan finished in 3.592s: 151015 files, 455.296 GiB Save(<data/94c5f19afe>) failed: write /mnt/backuphdd/restic/data/94/94c5f19afe5d5df59e1e3f6ad85098f69a9f5b1a4b88155bb9bdc0f7b562fd3b-tmp-3343818342: no space left on device Fatal: unable to save snapshot: write /mnt/backuphdd/restic/data/94/94c5f19afe5d5df59e1e3f6ad85098f69a9f5b1a4b88155bb9bdc0f7b562fd3b-tmp-3343818342: no space left on device Backup failed Forget about old snapshots based on RESTIC_FORGET_ARGS = --keep-last 10 --keep-daily 7 --keep-weekly 5 --keep-monthly 12 Applying Policy: keep 10 latest, 7 daily, 5 weekly, 12 monthly snapshots Finished backup at 2025-01-20 15:13:25 after 453 seconds
NCDU showing storage spaces.
Beta Was this translation helpful? Give feedback.
All reactions