While deploying SigNoz using the new foundryctl tool, I hit the ultimate developer roadblock: Docker input/output crashes and a persistent 5-minute image download timeout. Here is exactly how I bypassed these hurdles, pre-loaded the Docker cache, and successfully spun up a live OpenTelemetry dashboard.

The Goal

I wanted to run a local instance of SigNoz to monitor application telemetry without relying on cloud-hosted solutions.

The Roadblocks (WSL & Docker Timeouts)

During the foundryctl cast setup, my WSL 2 environment started throwing -bash: /usr/bin/docker: Input/output error.

The Fix: A quick wsl --shutdown in PowerShell and a full restart of Docker Desktop synced the engine back up.

However, the bigger issue was the ClickHouse database. SigNoz relies on heavy database layers, and the Foundry installation script has a strict 5-minute timeout. My network couldn't pull the massive ClickHouse images fast enough, causing the entire installation to crash at the 5-minute mark.

The Solution: Pre-loading the Cache

Instead of letting the script time out, I bypassed it by opening a standard Windows Command Prompt (outside of WSL) and manually pulling the heaviest images directly into Docker Desktop beforehand.

docker pull clickhouse/clickhouse-server:24.3-alpine

By the time I ran foundryctl cast -f casting.yaml again, the images were already cached. The setup bypassed the download phase entirely and spun up the containers instantly!

Generating Live Traffic

An empty dashboard is boring. To prove the ingestion engine was working, I used a telemetry generator to blast test data into the local instance.

docker run --rm ghcr.io/open-telemetry/opentelemetry-collector-contrib/telemetrygen:latest traces --otlp-insecure --otlp-endpoint host.docker.internal:4317 --rate 100 --duration 10m

As you can see in the dashboard, the local SigNoz instance effortlessly handled over 24,000 calls at 50+ ops/sec with a 0.00% error rate.

Conclusion

Deploying heavy data tools locally takes patience, especially when fighting WSL and Docker configurations. But by understanding how to manually manage your Docker cache and bypass script timeouts, you can run enterprise-grade observability right on your laptop.

Acknowledgments

To complete this deployment and debug the WSL/Docker conflicts, I used Google Gemini as an AI collaborator. It helped me troubleshoot terminal input/output errors, and little bit assisted in structuring this technical documentation.