Clarify that docker secret manages Swarm secrets #3309
+15
−15
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.
docker secretcommand is a swarm-specific secret implementation where secrets are stored in swarm managers and only made available to services via swarm worker agents. Unfortunately, the command was not put underdocker swarmsubcommand and therefore leads to confusion when managing other types of secrets(eg. build secrets). Make it clear that these are Swarm secrets without requiring the user to read through the whole documentation.Signed-off-by: Tonis Tiigi tonistiigi@gmail.com