ClickHouse/docker
Azat Khuzhin 25e3bebd9d Rework core collecting on CI (eliminate gcore usage)
gcore is a gdb command, that internally uses gdb to dump the core.

However with proper configuration of limits (core_dump.size_limit) it
should not be required, althought some issues is possible:
- non standard kernel.core_pattern
- sanitizers

So yes, gcore is more "universal" (you don't need to configure any
`kernel_pattern`), but it is ad-hoc, and it has drawbacks -
**it does not work when gdb fails**. For example gdb may fail with
`Dwarf Error: DW_FORM_strx1 found in non-DWO CU` in case of DWARF-5 [1].

  [1]: https://github.com/ClickHouse/ClickHouse/pull/40772#issuecomment-1236331323.

Let's try to switch to more native way.

Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
2022-09-04 22:07:16 +02: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 ci: add symlink for llvm-symbolizer (to make symbolizer work) 2022-09-04 14:03:34 +02:00
server Remove the remaining parts of "unbundled" build 2022-08-27 02:18:47 +02:00
test Rework core collecting on CI (eliminate gcore usage) 2022-09-04 22:07:16 +02: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.