Hello,
I encountered an immediate crash when trying to run the mcp/clickhouse:latest Docker image (https://hub.docker.com/r/mcp/clickhouse) on a standard x86_64 server.
1. Observed Behavior:
The container immediately exits with Exit Code 132. When running the entrypoint command manually inside the container, it produces:
Illegal instruction (core dumped)
2. Diagnosis (Root Cause):
The error indicates that the application (or a linked library) is attempting to execute a CPU instruction not supported by the host hardware. My diagnosis is that the image is built with optimizations for advanced instruction sets (such as AVX2 or similar modern extensions) that are not available on all x86_64 host environments (e.g., older CPUs or highly-virtualized cloud instances).
3. Version Discrepancy (Possible Contributor):
Upon inspection, the latest image is built using Python 3.13.9, which is a highly recent version. This may have led to the aggressive compiler optimizations that caused the compatibility issue. I noticed the project's .python-version or similar configuration might suggest using a more stable version, such as Python 3.10.
Request:
Could you please consider:
- Rebuilding the
latest tag using a more stable Python version (e.g., 3.10) to ensure wider compatibility.
- Or, providing a separate tag (e.g.,
mcp/clickhouse:compatible or mcp/clickhouse:no-avx) built with compiler flags that prioritize generic CPU compatibility over maximum performance (e.g., by disabling AVX/AVX2 optimizations).
Thank you for your time and assistance!
[This text was translated and refined by gemini-2.5-flash.]
Hello,
I encountered an immediate crash when trying to run the
mcp/clickhouse:latestDocker image (https://hub.docker.com/r/mcp/clickhouse) on a standard x86_64 server.1. Observed Behavior:
The container immediately exits with
Exit Code 132. When running the entrypoint command manually inside the container, it produces:Illegal instruction (core dumped)2. Diagnosis (Root Cause):
The error indicates that the application (or a linked library) is attempting to execute a CPU instruction not supported by the host hardware. My diagnosis is that the image is built with optimizations for advanced instruction sets (such as AVX2 or similar modern extensions) that are not available on all x86_64 host environments (e.g., older CPUs or highly-virtualized cloud instances).
3. Version Discrepancy (Possible Contributor):
Upon inspection, the
latestimage is built using Python 3.13.9, which is a highly recent version. This may have led to the aggressive compiler optimizations that caused the compatibility issue. I noticed the project's.python-versionor similar configuration might suggest using a more stable version, such as Python 3.10.Request:
Could you please consider:
latesttag using a more stable Python version (e.g., 3.10) to ensure wider compatibility.mcp/clickhouse:compatibleormcp/clickhouse:no-avx) built with compiler flags that prioritize generic CPU compatibility over maximum performance (e.g., by disabling AVX/AVX2 optimizations).Thank you for your time and assistance!
[This text was translated and refined by gemini-2.5-flash.]