Replies: 1 comment 1 reply
-
It's harmless, and I would leave it be. Modern (v2) Compose CLI, is just a single binary that acts as a Docker CLI plugin, and doesn't affect Swarm Mode or Docker Engine by just being installed. I would leave the defaults and I've never seen someone bother to uninstall it on servers. It'll just get upgraded when a |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
First, thank you so much for the answer to the swarm vs compose question. That also applied in my case. We have a critical but low-load ELK + custom python server and will probably also start the same way, but sometime in the next year add some HA redundancy just to be more safe, after more familiarity with the simpler single-node setup.
What is your recommended installation / method for a simple Swarm node? I have been using the get.docker.com script to get started, but that includes Docker Compose; do you see that as a problem (in terms of avoiding having to keep it up to date, even if not used)?
Or perhaps the simplest is to use the script and then just uninstall Docker Compose? Or something like that?
I suspect a minimum Swarm node is similar to the script but with Docker Compose uninstalled? If so, should I uninstall just the last two of these or all three? Or can I just ignore their installation as benign?
Actually that was a list of available, and only
docker-compose-plugin
is installed. Safe to leave? Safe to remove?Beta Was this translation helpful? Give feedback.
All reactions