Altinity Stable Builds Docker Install Guide
Installation Instructions: Docker
These included instructions detail how to install a single Altinity Stable build of ClickHouse container through Docker. For details on setting up a cluster of Docker containers, see ClickHouse on Kubernetes.
Docker Images are available for Altinity Stable builds and Community builds. The instructions below focus on using the Altinity Stable builds for ClickHouse.
IMPORTANT NOTEThe Altinity Stable builds for ClickHouse do not use the
latesttag. We highly encourage organizations to install a specific version of Altinity Stable builds to maximize compatibility. For information on the latest Altinity Stable Docker images, see the Altinity Stable for ClickHouse Docker page.
The Docker repositories are located at:
- Altinity Stable builds: altinity/clickhouse-server
To install a ClickHouse Altinity Stable build through Docker:
Create the directory for the docker-compose.yml file and the database storage and ClickHouse server storage.
mkdir clickhouse cd clickhouse mkdir clickhouse_database
Create the file
docker-compose.ymland populate it with the following, updating the
clickhouse-serverto the current
version: '3' services: clickhouse_server: image: altinity/clickhouse-server:22.214.171.124.altinitystable ports: - "8123:8123" volumes: - ./clickhouse_database:/var/lib/clickhouse networks: - clickhouse_network networks: clickhouse_network: driver: bridge ipam: config: - subnet: 10.222.1.0/24
Launch the ClickHouse Server with
docker composedepending on your version of Docker:
docker compose up -d
Verify the installation by logging into the database from the Docker image directly, and make any other necessary updates with:
docker compose exec clickhouse_server clickhouse-client root@67c732d8dc6a:/# clickhouse-client ClickHouse client version 126.96.36.199.altinity+stable (altinity build). Connecting to localhost:9000 as user default. Connected to ClickHouse server version 21.1.10 revision 54443. 67c732d8dc6a :)
Was this page helpful?
Glad to hear it!
Sorry to hear that. We'll track this issue and see how we can improve.