thank you for the hints, You might want to use docker config ls | grep myconfig-prefix-string | awk ' { print $2 } ' | xargs -I{} docker config rm {} to clean up the older configs, otherwise you will end up with tons of docker configs
I don’t like that Design of docker swarm to be really honest: - first of all I simply can’t change the content of the configs when they are not linked to a external file. Which is especially dumb if you have 3 masters and you need to make sure that this file is there in the correct state. - every time I change the configuration file I also need to change that compose so swarm notice the difference. Because it doesn’t diff the config with the config file, no I just diffs the compose file. - yeah you can also script that and corn that but that is far away from being native and elegant. Too many “bells and whistles” which need to maintained separately instead of having some integrated and native. What also upsets me on services: the handling of volumes. Why in the hell are volumes located on just the node running that service, if the container is changing the node the volume is not there. There have been a couple of very dumb design flaws that make it annoying to maintain a docker swarm
An external secrets name can’t be controlled inside a stack file. If you mark a config/secret/network/volume “external” then you have to manually manage those objects.
Great video! I'm wondering if you could prepare less for it? Or if someone could.
thank you for the hints,
You might want to use
docker config ls | grep myconfig-prefix-string | awk ' { print $2 } ' | xargs -I{} docker config rm {}
to clean up the older configs, otherwise you will end up with tons of docker configs
thank you. Lately, I have had to deal with some of the DevOps tasks and that video helped me
I don’t like that Design of docker swarm to be really honest:
- first of all I simply can’t change the content of the configs when they are not linked to a external file. Which is especially dumb if you have 3 masters and you need to make sure that this file is there in the correct state.
- every time I change the configuration file I also need to change that compose so swarm notice the difference. Because it doesn’t diff the config with the config file, no I just diffs the compose file.
- yeah you can also script that and corn that but that is far away from being native and elegant. Too many “bells and whistles” which need to maintained separately instead of having some integrated and native.
What also upsets me on services: the handling of volumes. Why in the hell are volumes located on just the node running that service, if the container is changing the node the volume is not there.
There have been a couple of very dumb design flaws that make it annoying to maintain a docker swarm
Hi Bret,
Is it applicable for external secrets or only can be used in file type secrets.
An external secrets name can’t be controlled inside a stack file. If you mark a config/secret/network/volume “external” then you have to manually manage those objects.