Hello,
I am surprise that the config functionnality does not allow to edit. Seems that the only way is to delete & recreate :
I liked the idea, but seems that mount is more flexible.
Am I missing something here ?
Thank you
This is a swarm feature, and as such is used to make config files available on any cluster node that could potentially deploy the swarm task. The same is true for secrets, just with the difference that they are stored encrypted at rest in the cluster state.
With swarm, your docker client can run on a host that is not part of the swarm cluster, and still deploy a config or secret based on a local file from the host, without having to have the file available through the filesystem of every cluster node.
On a single node, neither configs, nor secrets really have a benefit compared to binding the files in read-only mode.
There is one benefit, you can inline the config into a single compose file (example), no need for multiple files.
1 Like
I haven’t though about that! Good point!