I
Immich•2mo ago
p3lim

FATAL: role "immich" does not exist

wanted to give this project a try, copied the compose example (but removed the machine learning part because of hardware constraints), and when spinning this up the server container just crash loops and the message "FATAL: role "immich" does not exist" repeats in the postgres logs. there were no manual init steps mentioned in the quick start so I assumed this would just work out of the box
12 Replies
Immich
Immich•2mo ago
:wave: Hey @p3lim, 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. :blue_square: reviewed Github for known issues. 5. :blue_square: tried accessing Immich via local ip (without a custom reverse proxy). 6. :blue_square: uploaded the relevant information (see below). 7. :blue_square: 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.
Zeus
Zeus•2mo ago
Post your compose and env please
p3lim
p3limOP•2mo ago
services:
immich:
image: ghcr.io/immich-app/immich-server:v2.1.0
restart: unless-stopped
volumes:
- /etc/localtime:/etc/localtime:ro
- /store/data/immich/server:/data
environment:
DB_HOSTNAME: postgres
DB_USERNAME: postgres
DB_PASSWORD_FILE: /run/secrets/postgres_password
secrets:
- postgres_password
depends_on:
postgres:
condition: service_healthy
redis:
condition: service_healthy

redis:
image: docker.io/valkey/valkey:8.1.4-alpine # redis fork
restart: unless-stopped
healthcheck:
test: redis-cli ping || exit 1

postgres:
image: ghcr.io/immich-app/postgres:14-vectorchord0.5.3-pgvector0.8.1
restart: unless-stopped
shm_size: 128mb # shared memory limit
volumes:
- /store/data/immich/db:/var/lib/postgresql/data
environment:
POSTGRES_DB: immich
POSTGRES_USER: postgres
POSTGRES_PASSWORD_FILE: /run/secrets/postgres_password
POSTGRES_INITDB_ARGS: '--data-checksums'
secrets:
- postgres_password
healthcheck:
test: ["CMD", "pg_isready", "-U", "immich"]
interval: 10s
start_period: 30s

secrets:
postgres_password:
file: secret-postgres.txt
services:
immich:
image: ghcr.io/immich-app/immich-server:v2.1.0
restart: unless-stopped
volumes:
- /etc/localtime:/etc/localtime:ro
- /store/data/immich/server:/data
environment:
DB_HOSTNAME: postgres
DB_USERNAME: postgres
DB_PASSWORD_FILE: /run/secrets/postgres_password
secrets:
- postgres_password
depends_on:
postgres:
condition: service_healthy
redis:
condition: service_healthy

redis:
image: docker.io/valkey/valkey:8.1.4-alpine # redis fork
restart: unless-stopped
healthcheck:
test: redis-cli ping || exit 1

postgres:
image: ghcr.io/immich-app/postgres:14-vectorchord0.5.3-pgvector0.8.1
restart: unless-stopped
shm_size: 128mb # shared memory limit
volumes:
- /store/data/immich/db:/var/lib/postgresql/data
environment:
POSTGRES_DB: immich
POSTGRES_USER: postgres
POSTGRES_PASSWORD_FILE: /run/secrets/postgres_password
POSTGRES_INITDB_ARGS: '--data-checksums'
secrets:
- postgres_password
healthcheck:
test: ["CMD", "pg_isready", "-U", "immich"]
interval: 10s
start_period: 30s

secrets:
postgres_password:
file: secret-postgres.txt
no env file
Zeus
Zeus•2mo ago
Your edits have caused it to break I think..
p3lim
p3limOP•2mo ago
I followed https://docs.immich.app/install/environment-variables/ hope I didn't mess anything up 🙏
Zeus
Zeus•2mo ago
You’re missing DB_DATABASE_NAME https://github.com/immich-app/immich/blob/main/docker/example.env Please refer again to our compose and env without any changes
p3lim
p3limOP•2mo ago
according to the docs it has the default value of "immich", which is why I didn't specify it still get the error with DB_DATABASE_NAME: immich defined
Zeus
Zeus•2mo ago
Something is messed up and I can clearly see you are not using our compose 🙂 Perhaps you started the DB without specifying the database name (that’s only set on first start)
p3lim
p3limOP•2mo ago
I'm running docker compose down -v && rm -rf /store/data/immich between each test
Zeus
Zeus•2mo ago
I recommend you use our default compose and see if that works first. Then you can edit one by one as you’d like.
p3lim
p3limOP•2mo ago
found the issue; I had two containers named "postgres" in the same docker network 🤦
Immich
Immich•2mo ago
This thread has been closed. To re-open, use the button below.

Did you find this page helpful?