ClickHouse/docker
Igor Nikonov dbfb448290 Fix: integration test, standalone keeper mode
There is logic regarding which keeper binary use to start keeper cluster in an integration test
There 2 options:
(1) standalone keeper binary (expected binary name clickhouse-keeper)
(2) clickhouse binary with keeper inside

Fixed:
- option (1) didn't work since docker_compose_keeper.yaml didn't create
target clickhouse-keeper at all
- if clickhouse-keeper existed, option (1) was taken but
  clickhouse-keeper could be just a link to clickhouse binary (the link
  is created always during build if cmake option BUILD_STANDALONE_KEEPER is OFF)
2022-09-09 14:51:34 +00:00
..
bare .tech -> .com 2021-09-22 03:22:57 +03:00
client Update version to 22.1 not 21.13 2022-01-14 15:10:45 +03:00
docs Add a way to invalidate docker images cache 2022-06-08 14:47:45 +02:00
keeper Fixes for clickhouse/clickhouse-keeper docker image (#38462) 2022-06-30 12:47:35 +02:00
packager fix: pass -DNO_SSE3_OR_HIGHER=1 from packager 2022-09-06 12:18:11 +00:00
server Delete old cache directories creation from entrypoint (#40946) 2022-09-04 23:54:05 +02:00
test Fix: integration test, standalone keeper mode 2022-09-09 14:51:34 +00:00
images.json Use test-util as source for base-test, fasttest and package builder 2022-08-03 14:49:06 +02:00
README.md Move integration tests docker files to docker/ directory. Rename image -> runner. 2020-04-17 19:01:16 +03:00

ClickHouse Dockerfiles

This directory contain Dockerfiles for clickhouse-client and clickhouse-server. They are updated in each release.

Also there is bunch of images for testing and CI. They are listed in images.json file and updated on each commit to master. If you need to add another image, place information about it into images.json.