docker-compose.yml withPostgres doesn' t work.

[hrugani]

I tried to create a self-hosting n8n using the docker-compose.yaml file for "WithPostgress".
I edited my .env file and changed the necessary values.
Positioning in the right directory for docker-compose/withPostgress and executing the command:

docker compose up -d

We tried both: docker compose subcommand present in the latest version of docker, and docker-compose cli as a direct command line. Both had the same behavior.
All seem to have been executed successfully. 2 containers appear up and running using the docker ps command.
But when I try to access the URL localhost:/5678 in any browser (Chrome, for example), the browser shows an error saying the URL isn't reachable. No service is listening in port 5678.

here are the logs from the n8n container:
log-n8n-container.log

I would appreciate any help with that subject.

[okayakdeniz]

Hello,

You may have run it with docker-compose up without changing the contents of the .env file at startup. When you fix the .env file and run it again, unfortunately, I guess it can't recover itself.

docker-compose down --volumes --remove-orphans
docker-compose up --build

you can run it again from the beginning.

If there are still problems,
Also, if you are running in Windows environment. It organises the file as CRLF to the .env file.

With Notepad ++ you can edit it as LF only and run it again.

I hope it will be useful for you.

[pentium10]

I had this issue myself, not sure why it doesn't work. I used the docker exec to run the command.

[dgruano]

I also encountered this problem. In case it helps anyone:

• Make sure you have downloaded the init-data.sh script
• Make sure your user follows the Postgres guidelines (e.g. I was using a username with uppercase characters that were converted to lowercase, so n8n could not access the DB with the uppercase credentials)

Otherwise, I agree with @okayakdeniz's suggestion on the cause and with @pentium10 with the potential solution.

[Fabio-Monti-02]

postgres:
image: postgres:16
restart: always
env_file:
- .env
# environment:
# - POSTGRES_USER
# - POSTGRES_PASSWORD
# - POSTGRES_DB
# - POSTGRES_NON_ROOT_USER
# - POSTGRES_NON_ROOT_PASSWORD
volumes:
- db_storage:/var/lib/postgresql/data
- ./init-data.sh:/docker-entrypoint-initdb.d/init-data.sh
healthcheck:
test: ['CMD-SHELL', 'pg_isready -h localhost -U ${POSTGRES_USER} -d ${POSTGRES_DB}']
interval: 5s
timeout: 5s
retries: 10
Making this change worked for me

[jsvensson]

Make sure that init-data.sh is executable, since Docker uses the file permissions from the host system. By default I got:

n8n-postgres-1  | /usr/local/bin/docker-entrypoint.sh: running /docker-entrypoint-initdb.d/init-data.sh
n8n-postgres-1  | /usr/local/bin/docker-entrypoint.sh: /docker-entrypoint-initdb.d/init-data.sh: /bin/bash: bad interpreter: Permission denied
n8n-postgres-1 exited with code 126

After doing chmod +x init-data.sh everything works just fine.

[Retoxx-dev]

Changing the encoding of init-data.sh from CRLF to LF fixed that issue for me.

EDIT: I'm using a Windows machine.

[IIIsToRmIII]

The problem lies in the indentation with spaces, which are changed by copying or editing the init-data.sh file. Spaces cannot be used for indentation; only tabs are allowed. Below is my solution for the init-data.sh file:

#!/bin/bash
set -e

if [ -n "${POSTGRES_NON_ROOT_USER:-}" ] && [ -n "${POSTGRES_NON_ROOT_PASSWORD:-}" ]; then
    SQL_COMMANDS=$(cat <<SQL
        CREATE USER "${POSTGRES_NON_ROOT_USER}" WITH PASSWORD '${POSTGRES_NON_ROOT_PASSWORD}';
        GRANT ALL PRIVILEGES ON DATABASE "${POSTGRES_DB}" TO "${POSTGRES_NON_ROOT_USER}";
        GRANT CREATE ON SCHEMA public TO "${POSTGRES_NON_ROOT_USER}";
SQL
    )
    echo "$SQL_COMMANDS" | psql -v ON_ERROR_STOP=1 --username "$POSTGRES_USER" --dbname "$POSTGRES_DB"
else
    echo "SETUP INFO: No Environment variables given!"
fi

Cheers!