## TL;DR

Implemented by maintainer timvisee: cluster bootstrap/topology configuration in the config file shipped first in the qdrant/qdrant:dev image and then in stable Qdrant 1.13.3. Reporter confirmed 'it works like a charm'.

## The error

```text
When deploying a multi-node Qdrant cluster with docker-compose / swarm / kubernetes, the initial cluster topology (bootstrap, peer URIs) could only be passed as CLI flags (--bootstrap, --uri), not configured in config.yaml, making containerized scaling awkward.
```

## Fix

1. Implemented by maintainer timvisee: cluster bootstrap/topology configuration in the config file shipped first in the qdrant/qdrant:dev image and then in stable Qdrant 1.13.3.
2. Reporter confirmed 'it works like a charm'.
3. Closed as completed.

Success check: the symptom above is gone and the original operation completes.

## When to use

- You hit this exact symptom in qdrant.
- You want the verified fix without digging through the thread.

## When not to use

- A different error in qdrant, even a similar-looking one.
- General qdrant setup or credential questions.

## Compatibility

- Qdrant (qdrant/qdrant)

## Variant phrasings

- How to fix "there is no the possibility to configure the initial cluster topology from the qdrant/config/config.yaml file" in qdrant
- qdrant: there is no the possibility to configure the initial cluster topology from the qdrant/config/config.yaml file

## Source

- https://github.com/qdrant/qdrant/issues/5880

---

## Vectle citations

- Exact version: <https://vectle.com/skills/skl_roktq_5Y8clK-8UiTW82iw/versions/skv_RiTnFODc0uQzmD2U8XxRoA>
- Canonical HTML skill page: <https://vectle.com/skills/skl_roktq_5Y8clK-8UiTW82iw>
- Current Markdown URL: <https://vectle.com/skills/skl_roktq_5Y8clK-8UiTW82iw/markdown>

## Selected public attribution and original notices/references

```json
{
  "author": "issueatlas",
  "client": null,
  "notices_and_references": [
    "https://github.com/qdrant/qdrant/issues/5880"
  ]
}
```