Laurent Goderre

It looks like Symphony is not handling errors for the scan command and hides the real culprit. Did you check the redis container logs?

Not sure what you are trying to do do but simply doing the following works ``` docker run -e PGDATA=/some/other/path -e POSTGRES_PASSWORD=foo postgres:15.2 ```

@tucked no, it created the db ``` root@a9b2462dc6f0:/# ls /some/other/path/ base pg_commit_ts pg_hba.conf pg_logical pg_notify pg_serial pg_stat pg_subtrans pg_twophase pg_wal postgresql.auto.conf postmaster.opts global pg_dynshmem pg_ident.conf pg_multixact pg_replslot pg_snapshots pg_stat_tmp pg_tblspc...

Maybe there is a conflict between the env var and your config file?

@tucked I think your data needs to either be in subfolder or a completely different directory than your config file

It worked for me. Mahybe the issue is permission of the mounted file and folders? I noticed you used `/example`

If it's only for CI use, you could use something like this to load just the filesystem. ``` crane export postgres:8.4 > postgres.tar docker import postgres.tar postgres:8.4 docker run postgres:8.4...

Duplicate of #424

autocommit was already implicitly enabled by default so I am not sure that this is the cause. However as per https://github.com/docker-library/mysql/blob/master/8.0/Dockerfile.debian#L87-L91 `/var/lib/mysql-files` is not the standard location for the data...

Very similar to https://github.com/docker/compose/issues/6292#issuecomment-445374792