Alexey Milovidov cdce6d70d5 Use persistent containers for DockerC ...

Start one idle Docker container per `DockerC` function at create time and
generate `docker exec -i <container> /user_func` for the `executable_pool`
command. This avoids creating and removing a Docker container for every pool
worker while preserving the container-level network, filesystem, capability,
memory, CPU, and pids restrictions.

The `drop` command removes the persistent container, and the stateless test
checks the generated `docker exec` command and container-name metadata without
requiring Docker.

PR: https://github.com/ClickHouse/ClickHouse/pull/105131

Tests:
- `python3 -m py_compile programs/server/user_defined_executable_function_drivers/c_driver_common.py`
- `CLICKHOUSE_BINARY=./build/programs/clickhouse tests/queries/0_stateless/04241_executable_udf_driver.sh`
- `CLICKHOUSE_BINARY=./build/programs/clickhouse tests/queries/0_stateless/04242_executable_udf_driver_errors.sh`

2026-05-17 00:14:41 +02:00

..

c_driver_common.py

Use persistent containers for DockerC

2026-05-17 00:14:41 +02:00

docker_c_create.sh

Split DockerC C-body driver runtimes

2026-05-16 23:44:55 +02:00

docker_c_drop.sh

Split DockerC C-body driver runtimes

2026-05-16 23:44:55 +02:00

gvisor_c_create.sh

Split DockerC C-body driver runtimes

2026-05-16 23:44:55 +02:00

gvisor_c_drop.sh

Split DockerC C-body driver runtimes

2026-05-16 23:44:55 +02:00

unsafe_c_create.sh

Split DockerC C-body driver runtimes

2026-05-16 23:44:55 +02:00

unsafe_c_drop.sh

Split DockerC C-body driver runtimes

2026-05-16 23:44:55 +02:00