You need to enable JavaScript to run this app.
优惠活动
大模型
产品
解决方案
定价
更多

ClickHouse集成测试Docker运行失败问题咨询:docker-compose文件缺失与镜像拉取超时

Solutions to Your ClickHouse Integration Test Issues with Docker

Let me walk you through fixing these problems step by step:

First, Answering Your Question 1

  • What does "fresh configured docker" mean?
    It refers to a Docker environment that's fully set up to work properly: Docker service is running, network connectivity is stable, user permissions are configured (so you don't have to use sudo every time), and it can pull images from registries without issues.
  • Does the yandex/clickhouse-integration-tests-runner image include all dependencies?
    Yes, it has all the core tools and dependencies needed to run ClickHouse integration tests. However, some specific tests (like test_odbc_interaction you're running) rely on external services (like MySQL), so the runner will automatically try to pull those third-party images when needed—that's why you ran into the second error.

Fixing the "Can't find docker-compose.yml" Error

  1. Check if docker-compose is installed
    Run docker-compose --version to confirm. If it's missing, install it first (your Docker version 17.06 might not include it by default).
  2. Verify file paths and working directory
    The error suggests the runner can't locate the docker-compose config files. This might happen because:
    • You're using sudo, which changes the working directory or environment variables. Try running the script without sudo (after adding your user to the docker group—see the tip below).
    • Double-check that the path /ClickHouse/tests/integration/test_odbc_interaction exists in your local setup, and that the docker_compose_mysql.yml file is present under the /compose subdirectory relative to the test folder.
  3. Confirm your ClickHouse build paths are correct
    Make sure the --binary, --bridge-binary, and --base-configs-dir flags point to valid, existing files in your build directory.

Fixing the MySQL Image Pull Timeout Error

This is a common network issue when accessing Docker Hub from regions with slow connectivity. Here's how to fix it:

  1. Add domestic Docker registry mirrors
    Create or edit the Docker daemon config file:
    sudo nano /etc/docker/daemon.json
    
    Paste these mirror addresses (pick one or multiple):
    {
      "registry-mirrors": ["https://mirror.aliyuncs.com", "https://hub-mirror.c.163.com"]
    }
    
  2. Restart Docker to apply changes
    sudo systemctl daemon-reload
    sudo systemctl restart docker
    
  3. Test pulling the MySQL image manually
    Run docker pull mysql:5.7 to confirm the mirror is working before re-running your test script.

Extra Tips

  • Avoid using sudo for Docker commands
    Add your user to the docker group to skip sudo and avoid environment/permission issues:
    sudo usermod -aG docker $USER
    
    Log out and back in for the changes to take effect.

内容的提问来源于stack exchange,提问作者GeekLee

相关产品推荐
方舟 Agent Plan

超全模态模型 × Harness 升级,最新支持 Deepseek-V4.1-Flash、GLM-5.3 系列、Doubao-Seedream-5.0-pro、Kimi-K3 (部分), 限时 9.9 元起

最近更新时间:2026.04.29 09:22:42