So like to mention the following:

WARNING: The PREFECT_SERVER_DB_CMD variable is not set. Defaulting to a blank string.
WARNING: The DB_CONNECTION_URL variable is not set. Defaulting to a blank string.
WARNING: The POSTGRES_DB variable is not set. Defaulting to a blank string.
WARNING: The POSTGRES_PASSWORD variable is not set. Defaulting to a blank string.
WARNING: The POSTGRES_USER variable is not set. Defaulting to a blank string.

has to do with env vs export (shell vs bash), I've added added a

.env

file with the postgres var information and that actually worked when running

docker-compose up

searched it and it has to do with docker-compose. Not sure if its a bug in server.py Docker docker-compose environment vars Maybe someone is able to verify?

Hi Jesper -thanks for sharing this. It looks like there is an issue with how we spawn the subprocess that calls docker compose that isn’t compatible with your OS. Would you mind opening an issue explaining what you've learned here and we'll see if we can update the subprocess environment.

In the server.py added some code to generate a .env file, postgres starts but now running into graphql issues (they already existed) it has something to do with the bash/sh env and docker

graphql_1   | bash: -c: line 0: syntax error near unexpected token `&&'
graphql_1   | bash: -c: line 0: ` && python src/prefect_server/services/graphql/server.py'