{"slug": "install-signoz-on-docker-standalone-self-host-guide", "title": "Install SigNoz on Docker Standalone - Self-Host Guide", "summary": "SigNoz released a self-host guide for installing its open-source observability platform on Docker standalone using Docker Compose. The guide walks users through installing foundryctl, creating a casting.yaml configuration file, and deploying the stack to run SigNoz on a single machine. The installation includes components like ClickHouse, PostgreSQL, and the SigNoz UI, with optional support for an MCP server to enable AI client queries.", "body_md": "This guide explains how to install SigNoz on Docker using Docker Compose. It runs all the components SigNoz requires on a single machine, making it the quickest way to get started with SigNoz.\n\nPrerequisites\n\n- A Linux or macOS machine. Microsoft\n`Windo`\n\nws is not officially supported. [Docker Engine](https://docs.docker.com/engine/install/)20.10+ (or Docker Desktop) with the[Docker Compose](https://docs.docker.com/compose/install/)v2 plugin.- At least 4GB of memory allocated to Docker.\n- Open ports:\n`8080`\n\n(SigNoz UI),`4317`\n\nand`4318`\n\n(OTLP ingestion), and`8000`\n\nif you enable the MCP server.\n\nInstall SigNoz\n\nStep 1: Install foundryctl\n\n```\ncurl -fsSL https://signoz.io/foundry.sh | bash\n```\n\nFor manual install (Windows PowerShell, air-gapped, etc.) or PATH setup, see the [foundry getting-started guide](https://github.com/SigNoz/foundry/blob/main/docs/getting-started.md).\n\nStep 2: Create casting.yaml\n\nCreate a casting file that targets Docker with `flavor: compose`\n\nand `mode: docker`\n\n:\n\n```\napiVersion: v1alpha1\nkind: Installation\nmetadata:\n  name: signoz\nspec:\n  deployment:\n    flavor: compose\n    mode: docker\n```\n\nFor all configuration options, see the [casting file reference](https://github.com/SigNoz/foundry/blob/main/docs/reference/casting-file.md) and the [Docker Compose example](https://github.com/SigNoz/foundry/tree/main/docs/examples/docker/compose).\n\nStep 3: Deploy\n\n```\nfoundryctl cast -f casting.yaml\n```\n\n`cast`\n\nvalidates Docker, generates the Compose files into `pours/deployment/`\n\n, and starts the containers.\n\nStep 4: Verify the installation\n\nCheck that the containers are running:\n\n```\ndocker ps\n```\n\nThe output should look similar to the following:\n\n```\nCONTAINER ID   IMAGE                                 COMMAND                  CREATED              STATUS                        PORTS                                                             NAMES\n315e746cf0ff   clickhouse/clickhouse-server:25.5.6   \"/entrypoint.sh\"         About a minute ago   Up About a minute (healthy)   8123/tcp, 9000/tcp, 9009/tcp                                      signoz-telemetrystore-clickhouse-0-0\n066dc6f6346f   postgres:16                           \"docker-entrypoint.s…\"   About a minute ago   Up About a minute (healthy)   5432/tcp                                                          signoz-metastore-postgres-0\ne3b456480fe4   clickhouse/clickhouse-keeper:25.5.6   \"/usr/bin/clickhouse…\"   About a minute ago   Up About a minute (healthy)   2181/tcp, 9181/tcp, 10181/tcp, 44444/tcp                          signoz-telemetrykeeper-clickhousekeeper-0\n51f763006ae0   signoz/signoz-otel-collector:latest   \"/bin/sh -c '/signoz…\"   About a minute ago   Up About a minute             0.0.0.0:4317-4318->4317-4318/tcp, [::]:4317-4318->4317-4318/tcp   signoz-ingester-1\nc7550a1412d4   signoz/signoz:latest                  \"./signoz server\"        About a minute ago   Up About a minute (healthy)   0.0.0.0:8080->8080/tcp, [::]:8080->8080/tcp                       signoz-signoz-0\n```\n\nOnce all containers are running, point your browser to `http://<IP-ADDRESS>:8080/`\n\nto access the SigNoz UI (use `http://localhost:8080/`\n\nwhen SigNoz runs on your local machine).\n\nStep 5: Enable the SigNoz MCP server (optional)\n\nFoundry can also deploy the [SigNoz MCP server](https://github.com/SigNoz/foundry/blob/main/docs/concepts/mcp-server.md) alongside the stack so AI clients can query your telemetry. It is disabled by default.\n\n-\nAdd an\n\n`mcp`\n\nblock under`spec`\n\nin`casting.yaml`\n\n:\n\n```\napiVersion: v1alpha1\nkind: Installation\nmetadata:\n  name: signoz\nspec:\n  deployment:\n    flavor: compose\n    mode: docker\n  mcp:\n    spec:\n      enabled: true\n```\n\n-\nRe-run cast to add the\n\n`signoz-mcp`\n\nservice on port`8000`\n\n:\n\n```\nfoundryctl cast -f casting.yaml\n```\n\nVerify it is live:\n\n```\ncurl -fsS localhost:8000/livez && echo \" OK\"\n```\n\n-\nCreate an API key from a\n\n[service account](https://signoz.io/docs/manage/administrator-guide/iam/service-accounts/)(**Settings → Service Accounts**, requires** Admin**role). -\nAdd the server to your AI client. For example, with Claude Code:\n\n```\nclaude mcp add --scope user --transport http signoz http://localhost:8000/mcp \\\n  --header \"SIGNOZ-API-KEY: <your-api-key>\"\n```\n\n`<your-api-key>`\n\n: the key from step 3\n\nTo confirm the connection, run\n\n`/mcp`\n\ninside Claude Code and check that the`signoz`\n\nserver is listed as connected.\n\nFor other clients and example workflows, see [SigNoz MCP Server](https://signoz.io/docs/ai/signoz-mcp-server/) and [AI use cases](https://signoz.io/docs/ai/use-cases/).\n\nCustomize the installation\n\nEvery change follows the same loop: update `casting.yaml`\n\n, then re-run `foundryctl cast`\n\nto apply it.\n\n-\n**Component settings**(image, replicas, environment): set them in the component's`spec`\n\n. For example, to pin SigNoz to a specific release, set its image to a version tag:\n\n```\nspec:\n  signoz:\n    spec:\n      image: signoz/signoz:v0.128.0\n```\n\n-\n**Anything Foundry does not model**(memory limits, networks, volumes): add[patches](https://github.com/SigNoz/foundry/blob/main/docs/concepts/patches.md)under`spec.patches`\n\n. Do not edit the generated files in`pours/`\n\nby hand, since forge overwrites them.\n\nTroubleshooting\n\n[Troubleshooting](#troubleshooting)\n\nfoundryctl fails\n\nRe-run the failing command with `--debug`\n\nfor verbose logs.\n\nA container is unhealthy or the UI does not load\n\nCheck the component's logs using the generated Compose file:\n\n```\ndocker compose -f pours/deployment/compose.yaml logs -f signoz-signoz-0\n```\n\nContainers keep restarting\n\nIncrease the memory allocated to Docker. SigNoz needs at least 4GB.\n\nBy default, retention period is set to **7 days** for logs and traces, and **30 days** for metrics. To change this, navigate to the **General** tab on the **Settings** page of SigNoz UI.\n\nFor more details, refer to the [retention period guide](https://signoz.io/docs/userguide/retention-period/).", "url": "https://wpnews.pro/news/install-signoz-on-docker-standalone-self-host-guide", "canonical_source": "https://signoz.io/docs/install/docker", "published_at": "2026-06-24 00:00:00+00:00", "updated_at": "2026-06-25 10:15:42.875448+00:00", "lang": "en", "topics": ["developer-tools", "ai-tools"], "entities": ["SigNoz", "Docker", "Docker Compose", "foundryctl", "ClickHouse", "PostgreSQL", "MCP server"], "alternates": {"html": "https://wpnews.pro/news/install-signoz-on-docker-standalone-self-host-guide", "markdown": "https://wpnews.pro/news/install-signoz-on-docker-standalone-self-host-guide.md", "text": "https://wpnews.pro/news/install-signoz-on-docker-standalone-self-host-guide.txt", "jsonld": "https://wpnews.pro/news/install-signoz-on-docker-standalone-self-host-guide.jsonld"}}