Docker compose issues with pg_restore and running tests/cli about ichiran HOT 4 CLOSED

Sure, go ahead!

from ichiran.

I found a workaround! I simply asked pg_restore to ignore the roles (via --no-owner --no-privileges), deleted the docker/pgdata, rebuilt the container and reran compose, and everything works!

So step 1, apply this patch:

diff --git a/docker/postgres-initdb/ichiran-db.sh b/docker/postgres-initdb/ichiran-db.sh
index dbe2c55..8aa9800 100644
--- a/docker/postgres-initdb/ichiran-db.sh
+++ b/docker/postgres-initdb/ichiran-db.sh
@@ -4,7 +4,7 @@ echo "========================="
 
 createdb -E 'UTF8' -l 'ja_JP.utf8' -T template0 dummy
 set +e
-pg_restore -C -d dummy /ichiran.pgdump
+pg_restore -C -d dummy /ichiran.pgdump --no-owner --no-privileges
 
 echo "========================="
 echo "Finished ichiran DB init!"

Then,

$ rm docker/pgdata && docker-compose build pg && docker compose up

I waited about ~half hour, watched du -h -d0 docker/pgdata tick up to 4.4 GB, before everything was ready.

I'm not a Postgres expert, any tips on what impact --no-owner --no-privileges has? Can I possibly create the ichiran role now, that the database has initialized, and then future restores will work unmodified? Or is the best thing to do is for the release process to somehow include roles in the dump file?

from ichiran.

I believe "role doesn't exist" error is normal and shouldn't affect anything. It's expected when restoring a database dump on a different machine. I don't use docker myself so not sure about the other issues

from ichiran.

Thanks for confirming @tshatrov! Do you want a one-line PR with the fix I mentioned above to make the Docker instructions work?

from ichiran.