Hi,
I’m using the script from this repository: docker-entrypoint-initdb.d/001_timescaledb_tune.sh
When TimescaleDB + timescaledb-tools are installed via apt (packagecloud) on Debian-based images, the script fails because it expects:
/usr/local/bin/timescaledb-tune
but the package installs the binary at:
/usr/bin/timescaledb-tune
Reproduction
docker run --rm -it postgres:16.13-trixie bash -lc '
set -euxo pipefail
apt-get update
apt-get install -y --no-install-recommends wget curl gnupg ca-certificates=20250419
wget -qO /tmp/timescale-key.asc https://packagecloud.io/timescale/timescaledb/gpgkey
gpg --dearmor </tmp/timescale-key.asc >/usr/share/keyrings/timescaledb.gpg
echo "deb [signed-by=/usr/share/keyrings/timescaledb.gpg] https://packagecloud.io/timescale/timescaledb/debian/ trixie main" >/etc/apt/sources.list.d/timescaledb.list
apt-get update
apt-get install -y --no-install-recommends timescaledb-2-postgresql-16 timescaledb-2-loader-postgresql-16 timescaledb-tools
curl -fsSL -o /tmp/001_timescaledb_tune.sh https://raw.githubusercontent.com/timescale/timescaledb-docker/refs/heads/main/docker-entrypoint-initdb.d/001_timescaledb_tune.sh
bash /tmp/001_timescaledb_tune.sh
'
Actual result
Script fails with:
.../001_timescaledb_tune.sh: line 123: /usr/local/bin/timescaledb-tune: No such file or directory
Expected result
The script should work with package-installed timescaledb-tools and resolve timescaledb-tune from PATH instead of requiring a hardcoded /usr/local/bin/... path.
If this approach makes sense, I can open a PR to remove the hardcoded binary path and keep compatibility with existing setups.
Current workaround
ln -s /usr/bin/timescaledb-tune /usr/local/bin/timescaledb-tune
Hi,
I’m using the script from this repository:
docker-entrypoint-initdb.d/001_timescaledb_tune.shWhen TimescaleDB +
timescaledb-toolsare installed via apt (packagecloud) on Debian-based images, the script fails because it expects:/usr/local/bin/timescaledb-tunebut the package installs the binary at:
/usr/bin/timescaledb-tuneReproduction
Actual result
Script fails with:
.../001_timescaledb_tune.sh: line 123: /usr/local/bin/timescaledb-tune: No such file or directoryExpected result
The script should work with package-installed
timescaledb-toolsand resolvetimescaledb-tunefromPATHinstead of requiring a hardcoded/usr/local/bin/...path.If this approach makes sense, I can open a PR to remove the hardcoded binary path and keep compatibility with existing setups.
Current workaround