Docker image with 'pg_repack' (PostgreSQL extension) installed, can be run natively - or be used 'client-side' to run/invoke pg_repack functionality for a PostgreSQL database with the extension installed.

Reference: https://github.com/reorg/pg_repack

This images follows the pg_repack releases + compatibility with PostgreSQL.

https://hub.docker.com/r/hartmutcouk/pg-repack-docker/

docker build . -t pg-repack-docker

This image extends the official postgres docker image - so you can start a container with postgres following the official image.
e.g. pg11 (+pg_repack 1.4.4):

docker run -e POSTGRES_PASSWORD=1234 --name pg11 -p 5432:5432 -d hartmutcouk/pg-repack-docker:1.4.4

psql from local:

PGPASSWORD=supersecure psql -h localhost -U postgres

psql via docker:

docker run -e PGPASSWORD=supersecure -it --rm --network host hartmutcouk/pg-repack-docker:1.4.4 psql -h localhost -U postgres

docker run -e PGPASSWORD=supersecure -it --rm --network host hartmutcouk/pg-repack-docker:1.4.4 pg_repack -h localhost -U dbroot --dbname=dbname --dry-run --table=table1 --only-indexes --no-superuser-check

Notes:

• uses host network: --network host
• passing PGPASSWORD via env variable avoids password prompt (to e.g. exec via script/cron)