Immich•3mo ago

errors occur when setting the upload location to my windows D drive

Errors:

Error response from daemon: invalid volume specification: 'D:\New-Immich-Files\library:/usr/src/app/

Error response from daemon: invalid volume specification: 'D:\New-Immich-Files\library:/usr/src/app/

from terminal

<3>WSL (7531) ERROR: CreateProcessCommon:559: execvpe(C:\Program Files\Docker\Docker\resources\bin\docker.exe) failed: No such file or directory

<3>WSL (7531) ERROR: CreateProcessCommon:559: execvpe(C:\Program Files\Docker\Docker\resources\bin\docker.exe) failed: No such file or directory

from docker desktop .yaml - using the standard .yaml file with the added

pgdata:

pgdata:

at the bottom My .env

# You can find documentation for all the supported env variables at https://immich.app/docs/install/environment-vari>

# The location where your uploaded files are stored
UPLOAD_LOCATION="D:\New-Immich-Files\library"
# The location where your database files are stored
DB_DATA_LOCATION=pgdata

# To set a timezone, uncomment the next line and change Etc/UTC to a TZ identifier from this list: https://en.wikipe># TZ=Etc/UTC

# The Immich version to use. You can pin this to a specific version like "v1.71.0"
IMMICH_VERSION=release

# Connection secret for postgres. You should change it to a random password
# Please use only the characters `A-Za-z0-9`, without special characters or spaces
DB_PASSWORD=postgres

# The values below this line do not need to be changed
###################################################################################
DB_USERNAME=postgres
DB_DATABASE_NAME=immich

# You can find documentation for all the supported env variables at https://immich.app/docs/install/environment-vari>

# The location where your uploaded files are stored
UPLOAD_LOCATION="D:\New-Immich-Files\library"
# The location where your database files are stored
DB_DATA_LOCATION=pgdata

# To set a timezone, uncomment the next line and change Etc/UTC to a TZ identifier from this list: https://en.wikipe># TZ=Etc/UTC

# The Immich version to use. You can pin this to a specific version like "v1.71.0"
IMMICH_VERSION=release

# Connection secret for postgres. You should change it to a random password
# Please use only the characters `A-Za-z0-9`, without special characters or spaces
DB_PASSWORD=postgres

# The values below this line do not need to be changed
###################################################################################
DB_USERNAME=postgres
DB_DATABASE_NAME=immich

39 Replies

Immich•3mo ago

:wave: Hey @OOF, 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. :blue_square: 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:

OOFOP•3mo ago

have tried changing the directory formatting in a bunch of different ways. This used to work but since deleting and starting again it does not work it works when i allow the default paths. i think it might be an issue of the container accessing the host system but this has worked before ok it has now just started working for some reason i have not changed a thing and the terminal error has gone the wsl error in docker is still there though I get the

Error response from daemon: invalid volume specification: 'D:\New-Immich-Files\library:/usr/src/app/upload:rw'

Error response from daemon: invalid volume specification: 'D:\New-Immich-Files\library:/usr/src/app/upload:rw'

error when i do

docker compose up -d

docker compose up -d

but not when i start it throught the docker desktop gui using ubuntu for wsl

Immich•3mo ago

Successfully submitted, a tag has been added to inform contributors. :white_check_mark:

NoMachine•3mo ago

I'm not experienced with windows, but shouldn't you use / to separate paths? even on Windows? Also you didn't define a valid path for DB_DATA_LOCATION, unless you are already using a previously created volume

OOFOP•3mo ago

doesn't work with / or \ sadly even with a proper postgres path it doesn't work

Mraedis•3mo ago

Ah here we are

OOFOP•3mo ago

lol

Mraedis•3mo ago

Are you doing docker bla bla in the windows terminal

OOFOP•3mo ago

in my terminal with ubuntu as in docker compose up -d you mean?

Mraedis•3mo ago

yeah exactly - D:\New-Immich-Files\library:/usr/src/app/upload:rw seems to be the right specification not 100% sure there 🙃

OOFOP•3mo ago

for some reason it works fine when i run it through the docker desktop ui. I'm thinking maybe i need to give access or a permission that i have missed but i honestly dk

Mraedis•3mo ago

You could set it all up through WSL 🤔 all drives are mounted at /mnt so it'd be /mnt/d/new...

OOFOP•3mo ago

as in change the .env file to that directory? i tried that at some point and it didn't work either

OOFOP•3mo ago

message.txt

OOFOP•3mo ago

the postgres just never starts but no errors in the terminal

OOFOP•3mo ago

OOFOP•3mo ago

assuming this is correct anyway

Mraedis•3mo ago

Yeah but this is windows That sounds like your postgres is on windows which is NTFS which won't work For windows you'll want a docker volume See: https://immich.app/docs/install/requirements#special-requirements-for-windows-users

OOFOP•3mo ago

oh yea mb even when i have the postgres in ./ it doesn't work

Mraedis•3mo ago

./ is not the same as on a volume

OOFOP•3mo ago

oh it works when i leave that paths as default

Mraedis•3mo ago

Maybe for now, but it will fail in mysterious ways in the future

OOFOP•3mo ago

oh i see ok oh my good lord there is no way just did a fresh install. did the special requirements for windows users. and set my library as /mnt/d/New-Immich-Files/library and it now works i swear i have done this before ty sir

Mraedis•3mo ago

👍

OOFOP•3mo ago

now i just set my upload location to my old immich folder which already has photos on it. Nothing is displayed. any way to resolve this?

Zeus•3mo ago

you need to restore the old database. you can't just point it at the old folder

Immich•3mo ago

https://immich.app/docs/administration/backup-and-restore

OOFOP•3mo ago

would this be the correct way to mount the backup?

Mraedis•3mo ago

You don't mount backups 👀 I mean I guess you could

OOFOP•3mo ago

oh i was just following the thing and it said to mount it i think

Mraedis•3mo ago

Oh did we change that Sorry I did not see that update 😛

OOFOP•3mo ago

docker compose down -v  # CAUTION! Deletes all Immich data to start from scratch
## Uncomment the next line and replace DB_DATA_LOCATION with your Postgres path to permanently reset the Postgres database
# Remove-Item -Recurse -Force DB_DATA_LOCATION # CAUTION! Deletes all Immich data to start from scratch
## You should mount the backup (as a volume, example: `- 'C:\path\to\backup\dump.sql:/dump.sql'`) into the immich_postgres container using the docker-compose.yml
docker compose pull                               # Update to latest version of Immich (if desired)
docker compose create                             # Create Docker containers for Immich apps without running them
docker start immich_postgres                      # Start Postgres server
sleep 10                                          # Wait for Postgres server to start up
docker exec -it immich_postgres bash              # Enter the Docker shell and run the following command
# Check the database user if you deviated from the default. If your backup ends in `.gz`, replace `cat` with `gunzip`
cat < "/dump.sql" \
| sed "s/SELECT pg_catalog.set_config('search_path', '', false);/SELECT pg_catalog.set_config('search_path', 'public, pg_catalog', true);/g" \
| psql --dbname=postgres --username=<DB_USERNAME> # Restore Backup
exit                                              # Exit the Docker shell
docker compose up -d                              # Start remainder of Immich apps

docker compose down -v  # CAUTION! Deletes all Immich data to start from scratch
## Uncomment the next line and replace DB_DATA_LOCATION with your Postgres path to permanently reset the Postgres database
# Remove-Item -Recurse -Force DB_DATA_LOCATION # CAUTION! Deletes all Immich data to start from scratch
## You should mount the backup (as a volume, example: `- 'C:\path\to\backup\dump.sql:/dump.sql'`) into the immich_postgres container using the docker-compose.yml
docker compose pull                               # Update to latest version of Immich (if desired)
docker compose create                             # Create Docker containers for Immich apps without running them
docker start immich_postgres                      # Start Postgres server
sleep 10                                          # Wait for Postgres server to start up
docker exec -it immich_postgres bash              # Enter the Docker shell and run the following command
# Check the database user if you deviated from the default. If your backup ends in `.gz`, replace `cat` with `gunzip`
cat < "/dump.sql" \
| sed "s/SELECT pg_catalog.set_config('search_path', '', false);/SELECT pg_catalog.set_config('search_path', 'public, pg_catalog', true);/g" \
| psql --dbname=postgres --username=<DB_USERNAME> # Restore Backup
exit                                              # Exit the Docker shell
docker compose up -d                              # Start remainder of Immich apps

Mraedis•3mo ago

looks good 👍

OOFOP•3mo ago

bro is trying to terrify me

Mraedis•3mo ago

👻 boo

OOFOP•3mo ago

mfw it didn't work 💀

Immich•3mo ago

This thread has been closed. To re-open, use the button below.

Gaming

Programming

errors occur when setting the upload location to my windows D drive

Did you find this page helpful?