#support

Troubleshooting SigNoz Docker Setup Issue

TLDR Nishant had trouble running the Signoz docker setup after cleaning old version images. Srikanth suggested running migration for upgrading. After following the advice, Nishant successfully ran the setup.

3mo

Join the chat

Jun 28, 2023 (3 months ago)

Photo of md5-c6e8dc7fcdf178830b4933494eff7768

Nishant

09:46 AM

I am unable to run the signoz docker setup after cleaning old version images, container, network and volumes for docker via docker prune command
Commit on git

commit 2ee7817685cc921ffe295db3388bc1e370ee3d15 (HEAD -> main, origin/main)
Merge: 4a467435 803cfd1a
Author: Ankit Nayan <[email protected]>
Date:   Thu Jun 22 00:56:11 2023 +0530

    Merge pull request #2955 from SigNoz/release/v0.21.0
    
    Release/v0.21.0

Error while running docker-compose up -d

Creating network "clickhouse-setup_default" with the default driver
Creating zookeeper-1 ... done
Creating clickhouse  ... done
Creating query-service                             ... done
Creating clickhouse-setup_otel-collector_1         ... done
Creating clickhouse-setup_otel-collector-metrics_1 ... done

ERROR: for alertmanager  Container "e13908186a47" is unhealthy.
ERROR: Encountered errors while bringing up the project.

I have only commented out hotrod and load-hotrod in docker-compose.yaml

09:49

Nishant

09:49 AM

docker logs e13

Photo of md5-ce04a9988e2fd758a659dc55be6f2543

Srikanth

09:51 AM

When upgrade from version <= 0.18 to >= 0.19+ you need to run migration https://signoz.io/docs/operate/migration/upgrade-0.19/

Nishant

10:16 AM

Followed the doc and recreating containers after migration with docker-compose up -d done the job. Thanks

SigNoz Community

Built with ClickHouse as datastore, SigNoz is an open-source APM to help you find issues in your deployed applications & solve them quickly | Knowledge Base powered by Struct.AI

Indexed 825 threads (61% resolved)

Join Our Community Manage subscription

Similar Threads

SigNoz Install Script Errors

Nishant encountered errors with the install.sh script. Prashant suggested using `bash install.sh` or `./install.sh` instead of `sh`.

5mo

SigNoz Deployment Issue in Docker Swarm with NFS Share

sati encounters issues with setting up SigNoz in docker-swarm with an NFS share resulting in otel-collector crash and inaccessible GUI. Nick experienced a similar problem and shared a workaround.

6mo

Troubleshooting SigNoz Local Setup on M1 Mac

Sindhu had issues with their local SigNoz installation using Docker on an M1 Mac. Srikanth helped diagnose the problem. It was resolved by manually starting the ClickHouse container and then starting SigNoz via Docker Compose in the terminal.

6mo