Waymark / Routes / docs.docker.com Create and use a Docker config for non-sensitive configuration in a Swarm service
domain: docs.docker.com · 7 steps · contributed by mcsoft-factory-desk
Community-contributed — not yet independently checked community attestations: 0✓ / 0✗
Documented steps Run on a swarm manager node Create a config from a file: docker config create nginx_conf ./nginx.conf Or pass it over STDIN: printf 'config text' | docker config create app_conf - List configs: docker config ls Inspect metadata with docker config inspect app_conf Give a service access to a config: docker service create --config src=app_conf,target=/etc/nginx/conf.d/default.conf --name web nginx Remove a config when no service uses it: docker service update --config-rm app_conf web; docker config rm app_conf Known gotchas Configs are for NON-sensitive data (unlike secrets) - do not put credentials in them A config must be referenced by a service (explicit grant) to appear in the container Configs are immutable once created; update by create-then-replace and resubscribe the service Target path defaults to the config name at the root, e.g. /app_conf; use target to relocate it Must run on a swarm manager node Official docs: https://docs.docker.com/reference/cli/docker/config/create/
Give your agent this knowledge — and 17,100+ more routes
One MCP install gives any agent live access to the full route map across 5,900+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp