#Unable to get immich backup container working

1 messages ยท Page 1 of 1 (latest)

safe wave
#

I'm not sure why I'm running into a issue getting the backup container runnign

red deltaBOT
#

: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 immich.

References

Checklist

  1. :ballot_box_with_check: I have verified I'm on the latest release(note that mobile app releases may take some time).
  2. :ballot_box_with_check: I have read applicable release notes.
  3. :ballot_box_with_check: I have reviewed the FAQs for known issues.
  4. :ballot_box_with_check: I have reviewed Github for known issues.
  5. :ballot_box_with_check: I have tried accessing Immich via local ip (without a custom reverse proxy).
  6. :ballot_box_with_check: I have uploaded the relevant logs, docker compose, and .env files using the buttons below or the /upload command.
  7. :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.

red deltaBOT
safe wave
#

Also commenting out the backup container allows immich to run fine no issue

fathom snow
#

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

safe wave
fathom snow
#

That would make sense with the given results

safe wave
#

I have tried docker system prune -a

#

and restoring from a backup but still runinto this issue

fathom snow
#

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

safe wave
#

Docker desktop on my mac indicates I'm on the latest version

safe wave
fathom snow
#

The other one

safe wave
# fathom snow The other one

rm: /var/lib/docker/image/overlay2/layerdb/sha256/a2d7501dfb3541f3d736125cdfd748618194f60cbb5c63f4de67a92530899628: No such file or directory

fathom snow
#

Great lol

#

You are doing with sudo?

safe wave
#

ah no

safe wave
#

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

fathom snow
#

That doesn't sound good

#

What hardware is this running on?

safe wave
fathom snow
#

Is the SSD pretty old?

safe wave
#

it was sitting in my basement

safe wave
safe wave
#

to many variables ๐Ÿซ 

fathom snow
#

This is officially beyond my area of expertise now ๐Ÿ˜

safe wave
#

I'll try to tinker with it a bit later

fathom snow
#

From what I briefly read, yes that looks correct as well

safe wave
#

I just set up a cron script at the end for the time being