SigNoz / signoz

SigNoz is an open-source observability platform native to OpenTelemetry with logs, traces and metrics in a single application. An open-source alternative to DataDog, NewRelic, etc. 🔥 🖥. 👉 Open source Application Performance Monitoring (APM) & Observability tool
https://signoz.io
Other
18.99k stars 1.25k forks source link

Clickhouse installation using install.sh fails: failed to create shim task #3470

Open sonst-was opened 1 year ago

sonst-was commented 1 year ago

Bug description

Hi there,

I'm trying to get signoz running for testing in a LXC container.

Using the provided install.sh the installation fails with the following error message when trying to start the container signoz-clickhouse:

Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error setting rlimits for ready process: error setting rlimit type 6: operation not permitted: unknown

Running the install.sh as root does not change the result.

Expected behavior

The installation doesn't fail.

How to reproduce

  1. Setup fresh container
  2. Follow the install instruction here https://signoz.io/docs/install/docker/#install-signoz-using-the-install-script
  3. Run into the following error:
    
    🟡 Starting the SigNoz containers. It may take a few minutes ...

[+] Running 3/4 ✔ Container load-hotrod Running 0.0s ✔ Container hotrod Running 0.0s ✔ Container signoz-zookeeper-1 Running 0.0s ⠦ Container signoz-clickhouse Starting 2.7s Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error setting rlimits for ready process: error setting rlimit type 6: operation not permitted: unknown Waiting for all containers to start. This check will timeout in 1 seconds ....

+++++++++++ ERROR ++++++++++++++++++++++ 🔴 The containers didn't seem to start correctly. Please run the following command to check containers that may have errored out:

sudo docker-compose -f ./docker/clickhouse-setup/docker-compose.yaml ps -a Please read our troubleshooting guide https://signoz.io/docs/install/troubleshooting/ or reach us on SigNoz for support https://signoz.io/slack


## Version information 
* **Signoz version**: fresh clone from repo
* **Browser version**: n/a
* **Your OS and version**: Ubuntu 22.04 LTS
* **Your CPU Architecture**(ARM/Intel): ARM

## Additional context
Running the suggested docker-compose command yields the following result:

admin@signoz ~/signoz/deploy > sudo docker-compose -f ./docker/clickhouse-setup/docker-compose.yaml ps -a NAME IMAGE COMMAND SERVICE CREATED STATUS PORTS hotrod jaegertracing/example-hotrod:1.30 "/go/bin/hotrod-linu…" hotrod 11 days ago Up 17 minutes 8080-8083/tcp load-hotrod signoz/locust:1.2.3 "/docker-entrypoint.…" load-hotrod 11 days ago Up 17 minutes 5557-5558/tcp, 8089/tcp signoz-alertmanager signoz/alertmanager:0.23.3 "/bin/alertmanager -…" alertmanager 4 minutes ago Created
signoz-clickhouse clickhouse/clickhouse-server:23.7.3-alpine "/entrypoint.sh" clickhouse 17 minutes ago Created 0.0.0.0:8123->8123/tcp, :::8123->8123/tcp, 0.0.0.0:9000->9000/tcp, :::9000->9000/tcp, 0.0.0.0:9181->9181/tcp, :::9181->9181/tcp, 9009/tcp signoz-frontend signoz/frontend:0.28.0 "nginx -g 'daemon of…" frontend 4 minutes ago Created
signoz-logspout gliderlabs/logspout:v3.2.14 "/bin/logspout syslo…" logspout 17 minutes ago Created
signoz-otel-collector signoz/signoz-otel-collector:0.79.6 "/signoz-collector -…" otel-collector 17 minutes ago Created
signoz-otel-collector-metrics signoz/signoz-otel-collector:0.79.6 "/signoz-collector -…" otel-collector-metrics 17 minutes ago Created
signoz-query-service signoz/query-service:0.28.0 "./query-service -co…" query-service 4 minutes ago Created
signoz-zookeeper-1 bitnami/zookeeper:3.7.1 "/opt/bitnami/script…" zookeeper-1 17 minutes ago Up 17 minutes 0.0.0.0:2181->2181/tcp, :::2181->2181/tcp, 0.0.0.0:2888->2888/tcp, :::2888->2888/tcp, 0.0.0.0:3888->3888/tcp, :::3888->3888/tcp, 8080/tcp

Thank you for your bug report – we love squashing them!

welcome[bot] commented 1 year ago

Thanks for opening this issue. A team member should give feedback soon. In the meantime, feel free to check out the contributing guidelines.

aioue commented 1 month ago

@sonst-was did you resolve this? Having the same issue.