Repository navigation
docs: add Docker Swarm secrets guide - #224
Open
brahimrizq wants to merge 2 commits into
Open
brahimrizq wants to merge 2 commits into
brahimrizq wants to merge 2 commits into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What is this PR about?
Adds a Swarm Secrets guide under Core > Advanced, right after Cluster. The Cluster and Docker Compose pages link to it.
The guide explains the Viewing server selector: managers in one Swarm share secrets, while separate Swarms have separate secret stores. Workers can receive mounted secrets but cannot manage them.
The guide shows how to create secrets, copy their names, use them in a Stack deployment, check service usage, rotate them, and delete unused secrets. It explains Current and Rollback references, zero-replica services, and why Docker cannot return or edit a secret's content.
The MySQL example uses environment variables for existing secret names and mounts both password files. It also explains that
external: truebelongs to the stack configuration.Companion feature: Dokploy/dokploy#5943
Feature proposal: Dokploy/dokploy#5942
Publication depends on the feature above. Publish this guide when the implementation is accepted and the dashboard feature is available.
Checklist
mainbranch.Testing
pnpm install --frozen-lockfilepnpm biome cipnpm typecheckpnpm --filter=docs run types:checkpnpm run docs:builddocker stack configresolved both external secret names and kept both mounts. It rejected either missing name variable. This check did not deploy anything.The latest update adds six lines about multiple servers. MDX generation and the docs type check passed again. The related feature also passed 16 live Vagrant multi-server checks.
All checks above passed with Node 24.22.1 and pnpm 10.22.0. No dependency or lockfile changes.
Validation results
Screenshots