Immich•3y ago

Project name must not be empty

Hi, I am doing yet another install of immich.

This time, however, I am seeing a "project name must not be empty" returned when i run docker compose up -d

.env and yml attached

I am running the compose command from the root of a drive (i:) that I want to store all my immich assets on. The .yml and .env are in that root folder.

I googled this and found that I could add

COMPOSE_PROJECT_NAME=immich

COMPOSE_PROJECT_NAME=immich

to the .env and it then ran, but I would like to know why in each of the maybe 5 or so installs I have done so far that I have never seen the "project name must not be empty" error.

Thanks!

miknzauOP•10/18/23, 8:00 PM

Doing some experimenting, seems that it does not like to be run from the root of a drive. If I create a folder on the drive, say i:/immich and then move the .yml and .env into that and the compose it works fine. The issue is then though that I have all the files in i:/immich/immich which is not ideal

Alex Tran•10/18/23, 8:03 PM

have you had a chance to search on Google yet?

Alex Tran•10/18/23, 8:04 PM

you should add COMPOSE_PROJECT_NAME to the

.env

.env

file I believe, not the yml file

miknzauOP•10/18/23, 8:08 PM

yes sorry i meant it was in the .env file. But all my previous installs I didn't need to do that - is it simply a function of trying to start it from the root of a drive? In other words, if run from a sub-directory it just uses the sub dir name as the project name?

Mmiknzau yes sorry i meant it was in the .env file. But all my previous installs I didn'...

Alex Tran•10/19/23, 12:07 AM

Yes this is what I understand as well

jrasm91•10/19/23, 1:31 AM

The project name comes by default from the folder name, so the drive on Windows must not work. You can use -p "project name" or the env or "name: project name" in the compose file if using docker compose without a hyphen