So like to mention the following ```WARNING The PREFECT SERV

Question

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 <https docs docker com compose environment variables substitute environment variables in compose files|docker compose environment vars> Maybe someone is able to verify

Jenny · Answer

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 <https github com PrefectHQ prefect issues|opening an issue> explaining what you ve learned here and we ll see if we can update the subprocess environment

Jenny · Answer

It s also possible that you might be able to set your environment variables in the main process where you re calling prefect server start But I m not certain that would work

Jesper van Dijke · Answer

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 ` amp amp graphql 1 | bash c line 0 ` amp amp python src prefect server services graphql server py ```