You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug autorestic works perfectly fine on the local host, but when I use the exact same config in the docker image, it fails without any apparent reason...
Expected behavior
Work the same out and in the docker image.
Environment
OS: Fedora 40
Version: autorestic version 1.8.2
Restic version: restic 0.16.4 compiled with go1.21.6 on linux/amd64 (same in and outside the container)
Additional context
The docker output, note that it tries to initialize, but the repo is already initialized and contains backups. It was initialized with a check from the autorestic binary on the host.
❯ docker run --rm \
-v /var/www:/var/www \
-v $(pwd)/autorestic.yml:/data/autorestic.yml \
-v $(pwd)/.autorestic.env:/data/.autorestic.env \
cupcakearmy/autorestic \
autorestic -c /data/autorestic.yml check
Using config: /data/autorestic.yml
Using env: /data/.autorestic.env
Using lock: /data/.autorestic.lock.yml
Initializing backend "backblaze"...
Error: exit status 1
The host output:
❯ autorestic -c ./autorestic.yml check
Using config: /home/autorestic/autorestic.yml
Using env: /home/autorestic/.autorestic.env
Using lock: .autorestic.lock.yml
Everything is fine.
The text was updated successfully, but these errors were encountered:
Describe the bug
autoresticworks perfectly fine on the local host, but when I use the exact same config in the docker image, it fails without any apparent reason...Expected behavior
Work the same out and in the docker image.
Environment
autorestic version 1.8.2restic 0.16.4 compiled with go1.21.6 on linux/amd64(same in and outside the container)Additional context
The docker output, note that it tries to initialize, but the repo is already initialized and contains backups. It was initialized with a
checkfrom the autorestic binary on the host.The host output:
The text was updated successfully, but these errors were encountered: