mirror of
https://github.com/ClickHouse/ClickHouse.git
synced 2024-11-24 08:32:02 +00:00
dbfb448290
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) |
||
---|---|---|
.. | ||
bare | ||
client | ||
docs | ||
keeper | ||
packager | ||
server | ||
test | ||
images.json | ||
README.md |
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
.