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
Hi, first of all many thanks for the stellar work; the images scratch a huge itch. Upgrading docker envs with Postgres 13 which has less than a year now were unexpectedly breezy.
I’d just advise some changes to the readme on docker hub.
The upgrade potentially creates hints/script files e.g. for extension upgrades which get lost with --rm.
I’d remove the --rm from the recommended run and note that the corresponding files are available in the "upper dir" of the container after run, or even advise also mounting the upgrader work dir in.
For sufficient paranoia, --network none might instead be advisable since the upgrade does not need connectivity and it removes exfil concerns for closed envs.
pg_hba for docker envs, which will likely be a good part of the user base, needs some adaptation after upgrade.
potentially also the postgresql.conf? How do you handle that for your upgrades?
If you’d like to save time on these docs changes, I’d be happy to make the changes if you’re willing to accept pull reqs.
The text was updated successfully, but these errors were encountered:
Hi, first of all many thanks for the stellar work; the images scratch a huge itch. Upgrading docker envs with Postgres 13 which has less than a year now were unexpectedly breezy.
I’d just advise some changes to the readme on docker hub.
I’d remove the
--rm
from the recommended run and note that the corresponding files are available in the "upper dir" of the container after run, or even advise also mounting the upgrader work dir in.For sufficient paranoia, --network none might instead be advisable since the upgrade does not need connectivity and it removes exfil concerns for closed envs.
pg_hba for docker envs, which will likely be a good part of the user base, needs some adaptation after upgrade.
potentially also the postgresql.conf? How do you handle that for your upgrades?
If you’d like to save time on these docs changes, I’d be happy to make the changes if you’re willing to accept pull reqs.
The text was updated successfully, but these errors were encountered: