You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The issue is the postgres config file copied into the container is called postgres.conf but the command line expects postgresql.conf.
The copy line is COPY ["postgres.conf", "/etc/postgres.conf"] from here.
The command line for the docker compose file is: pStruct["command"] = "postgres -c \"max_connections=100\" -p ${POSTGRES_PORT} -c config_file=/etc/postgresql.conf" from here.
This is not an issue if POSTGRES_USE_VOLUME is set to false because of the mapping is set correctly to postgresql.conf
When a user tries to run Mythic with POSTGRES_USE_VOLUME=true the mythic_postgres container just restarts with the logs showing:
mythic_postgres | postgres: could not access the server configuration file "/etc/postgresql.conf": No such file or directory
I think the simplest fix would be to update the docker container to copy in the config to /etc/postgresql.conf and push a new container to the registry.
The text was updated successfully, but these errors were encountered:
The issue is the postgres config file copied into the container is called
postgres.conf
but the command line expectspostgresql.conf
.The copy line is
COPY ["postgres.conf", "/etc/postgres.conf"]
from here.The command line for the docker compose file is:
pStruct["command"] = "postgres -c \"max_connections=100\" -p ${POSTGRES_PORT} -c config_file=/etc/postgresql.conf"
from here.This is not an issue if
POSTGRES_USE_VOLUME
is set to false because of the mapping is set correctly to postgresql.confWhen a user tries to run Mythic with
POSTGRES_USE_VOLUME=true
themythic_postgres
container just restarts with the logs showing:I think the simplest fix would be to update the docker container to copy in the config to
/etc/postgresql.conf
and push a new container to the registry.The text was updated successfully, but these errors were encountered: