Dev Env setup Error [windows VSC dev container]

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.0s
Error response from daemon: Conflict. The container name "/immich_postgres" is already in use by container "218b211d332d9d6423e3000054c6f5cf63b98bb07a5ab6d33923
17fce64957a5". 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.0s
Error response from daemon: Conflict. The container name "/immich_postgres" is already in use by container "218b211d332d9d6423e3000054c6f5cf63b98bb07a5ab6d33923
17fce64957a5". You have to remove (or rename) that container to be able to reuse
that name.
I turned off the docker containers that run my user-installation https://i.vgy.me/vmZzNT.png 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> 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 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
7 Replies
Immich
Immich5d ago
:wave: Hey @shadowrs, Thanks for reaching out to us. Please carefully read this message and follow the recommended actions. This will help us be more effective in our support effort and leave more time for building Immich :immich:. References - Container Logs: docker compose logs docs - Container Status: docker ps -a docs - Reverse Proxy: https://immich.app/docs/administration/reverse-proxy - Code Formatting https://support.discord.com/hc/en-us/articles/210298617-Markdown-Text-101-Chat-Formatting-Bold-Italic-Underline#h_01GY0DAKGXDEHE263BCAYEGFJA Checklist I have... 1. :ballot_box_with_check: verified I'm on the latest release(note that mobile app releases may take some time). 2. :ballot_box_with_check: read applicable release notes. 3. :ballot_box_with_check: reviewed the FAQs for known issues. 4. :ballot_box_with_check: reviewed Github for known issues. 5. :ballot_box_with_check: tried accessing Immich via local ip (without a custom reverse proxy). 6. :ballot_box_with_check: uploaded the relevant information (see below). 7. :ballot_box_with_check: tried an incognito window, disabled extensions, 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) Information In order to be able to effectively help you, we need you to provide clear information to show what the problem is. The exact details needed vary per case, but here is a list of things to consider: - Your docker-compose.yml and .env files. - Logs from all the containers and their status (see above). - All the troubleshooting steps you've tried so far. - Any recent changes you've made to Immich or your system. - Details about your system (both software/OS and hardware). - Details about your storage (filesystems, type of disks, output of commands like fdisk -l and df -h). - The version of the Immich server, mobile app, and other relevant pieces. - Any other information that you think might be relevant. Please paste files and logs with proper code formatting, and especially avoid blurry screenshots. Without the right information we can't work out what the problem is. Help us help you ;) If this ticket can be closed you can use the /close command, and re-open it later if needed. Successfully submitted, a tag has been added to inform contributors. :white_check_mark:
shadowrs
shadowrsOP5d ago
by renaming the containers belonging to user-installation I got it the dev container running 👍🏽 but is that the right practice or is it expected that a dev enviroment + default installation is compatile to run side by side?
No description
Sergey Katsubo
Hey @shadowrs I stumbled across this as well. You can automate container renaming by adjusting .devcontainer 1. Create an additional my-compose-override.yml
services:
immich-server:
container_name: immich_server_dev
immich-machine-learning:
container_name: immich_machine_learning_dev
redis:
container_name: immich_redis_dev
database:
container_name: immich_postgres_dev
services:
immich-server:
container_name: immich_server_dev
immich-machine-learning:
container_name: immich_machine_learning_dev
redis:
container_name: immich_redis_dev
database:
container_name: immich_postgres_dev
2. Include it in devcontainer.json in dockerComposeFile:
...
"dockerComposeFile": [
"../docker/docker-compose.dev.yml",
"./server/container-compose-overrides.yml",
"./my-compose-override.yml"
],
...
...
"dockerComposeFile": [
"../docker/docker-compose.dev.yml",
"./server/container-compose-overrides.yml",
"./my-compose-override.yml"
],
...
This will fix name conflict. When this conflict is resolved, it's time for another clash: Error response from daemon: failed to set up container networking: driver failed programming external connectivity on endpoint immich_server_dev (...): Bind for 0.0.0.0:2283 failed: port is already allocated :dogekek:
shadowrs
shadowrsOP5d ago
Thank you! That info should go into the documentation for sure
Sergey Katsubo
Yup. Final override using 2284:2283 (+ other ports from ./docker/docker-compose.dev.yml)
services:
immich-server:
# Error response from daemon: Conflict. The container name "/immich_postgres" is already in use by container ...
container_name: immich_server_dev
# Error response from daemon: failed to set up container networking:
# driver failed programming external connectivity on endpoint immich_server_dev (...):
# Bind for 0.0.0.0:2283 failed: port is already allocated
ports: !override
- 9230:9230
- 9231:9231
- 2284:2283
immich-machine-learning:
container_name: immich_machine_learning_dev
redis:
container_name: immich_redis_dev
database:
container_name: immich_postgres_dev
services:
immich-server:
# Error response from daemon: Conflict. The container name "/immich_postgres" is already in use by container ...
container_name: immich_server_dev
# Error response from daemon: failed to set up container networking:
# driver failed programming external connectivity on endpoint immich_server_dev (...):
# Bind for 0.0.0.0:2283 failed: port is already allocated
ports: !override
- 9230:9230
- 9231:9231
- 2284:2283
immich-machine-learning:
container_name: immich_machine_learning_dev
redis:
container_name: immich_redis_dev
database:
container_name: immich_postgres_dev
shadowrs
shadowrsOP5d ago
Working! Great thanks dude
Sergey Katsubo
@shadow may I ping you for an advice on running devcontainer alongside with an existing Immich on the same host? Is it the right thing to created additional override to avoid conflicts? Maybe there are other options?

Did you find this page helpful?