#Unable to get immich backup container working
1 messages ยท Page 1 of 1 (latest)
:wave: Hey @safe wave,
Thanks for reaching out to us. Please follow the recommended actions below; this will help us be more effective in our support effort and leave more time for building Immich
.
References
- Container Logs:
docker compose logsdocs - Container Status:
docker compose psdocs - Reverse Proxy: https://immich.app/docs/administration/reverse-proxy
- Typesense: You can't fix this. Just wait until we get rid of it. Sorry.
Checklist
- :ballot_box_with_check: I have verified I'm on the latest release(note that mobile app releases may take some time).
- :ballot_box_with_check: I have read applicable release notes.
- :ballot_box_with_check: I have reviewed the FAQs for known issues.
- :ballot_box_with_check: I have reviewed Github for known issues.
- :ballot_box_with_check: I have tried accessing Immich via local ip (without a custom reverse proxy).
- :ballot_box_with_check: I have uploaded the relevant logs, docker compose, and .env files using the buttons below or the
/uploadcommand. - :ballot_box_with_check: I have tried an incognito window, cleared mobile app cache, logged out and back in, different browsers, etc. as applicable
(an item can be marked as "complete" by reacting with the appropriate number)
If this ticket can be closed you can use the /close command, and re-open it later if needed.
@safe wave uploaded
@safe wave uploaded
@safe wave uploaded
Successfully submitted, a tag has been added to inform contributors. :white_check_mark:
Sounds like you might have a partial download for the image. Maybe backup the database manually and then try cleaning the docker image cache and try again
Yeah this did happen my mac spontaniously crashed and rebooted
That would make sense with the given results
how do you clear docker image cache?
I have tried docker system prune -a
and restoring from a backup but still runinto this issue
You can try deleting the file it is trying to rename it to
The other thing that comes to mind is making sure you are using a fairly recent docker engine version
Docker version 24.0.6, build ed223bc
Docker desktop on my mac indicates I'm on the latest version
rm: /var/lib/docker/image/overlay2/layerdb/tmp/write-set-444694822: No such file or directory
The other one
rm: /var/lib/docker/image/overlay2/layerdb/sha256/a2d7501dfb3541f3d736125cdfd748618194f60cbb5c63f4de67a92530899628: No such file or directory
ah no
same result
I may just nuke docker desktop later and reinstall it from scratch
another possibility is my mac mini or its internal boot ssd is failing
recently when doing a docker compose up my postgress database went corroupt causing my typsesense database and postgress container to reboot a lot
latter when trying to docker compose up immich lost the database and treated it as a new install
I restored a backup making it stable for now
it is a 2011 mac mini
Is the SSD pretty old?
I'm not even sure if its the ssd my macs sata cable or mother board header
I'm also using opencore legacy patcher
to many variables ๐ซ
This is officially beyond my area of expertise now ๐
but a partial download could cause this issue correct?
I'll try to tinker with it a bit later
From what I briefly read, yes that looks correct as well
I just set up a cron script at the end for the time being