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.

Photo of Nishant
Nishant
Wed, 28 Jun 2023 09:46:53 UTC

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

Photo of Nishant
Nishant
Wed, 28 Jun 2023 09:49:47 UTC

docker logs e13

Photo of Srikanth
Srikanth
Wed, 28 Jun 2023 09:51:09 UTC

When upgrade from version <= 0.18 to >= 0.19+ you need to run migration

Photo of Nishant
Nishant
Wed, 28 Jun 2023 10:16:11 UTC

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