I already have Immich setup and running in Docker Desktop windows 11 for personal use. I was looking to setup the dev environment too in a VSC dev container When I run "Dev Containers: Rebuild and Reopen in Container" in VSC per the setup guide https://immich.app/docs/developer/devcontainers [issue 1] The container fails to start with this error:
[+] Running 1/3 - Container immich_redis Creating 0.0s - Container init Creating 0.0s ✘ Container immich_postgres Error respons... 0.0sError response from daemon: Conflict. The container name "/immich_postgres" is already in use by container "218b211d332d9d6423e3000054c6f5cf63b98bb07a5ab6d3392317fce64957a5". You have to remove (or rename) that container to be able to reuse that name.
[+] Running 1/3 - Container immich_redis Creating 0.0s - Container init Creating 0.0s ✘ Container immich_postgres Error respons... 0.0sError response from daemon: Conflict. The container name "/immich_postgres" is already in use by container "218b211d332d9d6423e3000054c6f5cf63b98bb07a5ab6d3392317fce64957a5". You have to remove (or rename) that container to be able to reuse that name.
Should I be trying to give a unique name to the dev postgres container? Maybe temporarily renaming my user-installed postgres before + after when I use the dev container?
docker rename <current_name> <new_name>
docker rename <current_name> <new_name>
Same for redis, renaming them is what the error messages suggests. Just wondering if renaming to avoid conflicts is the right practice to when I want to dev or run my user-mode installation?
[issue 2] After renaming the containers, I get a different dev container startup error in VSC:
failed to execute bake: read |0: file already closed
failed to execute bake: read |0: file already closed
full log here https://pastes.io/immich-dev-vsc EDIT: a docker desktop restart seems to have fixed this after renaming the user-installation-containers
my compose.yml and .env are defaults, except : - non-default postgres db password - a few volumes mounts for original image libraries - ml acceleration section uncommented for nvidiacuda