So I checked the config for the external drive again and discovered when it was remounted it had added a, “1” to the end of the drive name. I went back into the .env and changed the library location to reflect this. Restarted docker and it is now connecting again. Obviously it is not ideal to be using a external HDD, but I wanted to test immich out for a while before investing into a bigger self hosting rig for all my services.

Ultimately problem solved though

Drive was just connected with USB to mini PC so it was also unplugged and I had to remount it to the PC. I looked in the .env file and the path still looked good. I had considered this was an issue too. I figured that restarting docker with the drive properly mounted would fix this though. Still getting, “connection was reset,” though

I’ve accepted that the days of good Bond movies are over. The only ones ensuring high quality were those producers. I’m just glad they finished the Daniel Craig films before this fiasco started

I thought rd got shut down

This console generation has been a thorough failure. I have a ps5 which is great to play my ps4 games, but I will only be investing in PC from here on out. Hopefully they release a more powerful steam deck soon that can play my ps3 and xbox360 reliability