// the take
An official Docker wrapper around the Postgres image that bakes in TimescaleDB and runs timescaledb-tune on startup. It's for anyone who wants a time-series Postgres running in a container without hand-configuring the extension and tuning parameters themselves.
timescaledb-tune runs automatically on init and is cgroup-aware, so it tunes against the container's actual CPU/memory limits rather than the host's — a detail a lot of similar images get wrong. It's a thin layer on the official postgres image, so every env var and volume convention you already know still applies. It ships multiple PG major versions (16/17/18) plus nightly builds on both amd64 and arm64, which makes testing against upcoming TimescaleDB releases easy.
It's a single-instance convenience image with no story for replication, HA, or multi-node time-series setups — you're building that yourself on top. Telemetry is on by default, and turning it off after the cluster is already initialized requires a manual follow-up step rather than just setting the env var, which is an easy thing to miss in a prod rollout. There's nothing here about backup/restore or major-version upgrade paths, which is the part of running Postgres in containers that actually bites people. Secrets and password handling are entirely inherited from the base postgres image, so you get no extra hardening for running a database that's often holding operational metrics.
We read the README, the directory tree and a key source file in November 2026. Nobody pays to be listed. How we judge →