• Feedback
  • USEnglish
  • docker-compose or docker compose

Hello,

not to long ago, the update.sh script changed from using docker-compose standalone to the plugin docker compose, see https://mailcow.email/2022/06/07/%f0%9f%8c%95%f0%9f%90%84-moone-update-2022-the-docker-compose-v2-update-part-i-changes/

I did the update and actually removed docker-compose from my system as it was working fine for my other containers as well.

But now, the update script is seems to require it again:

$ ./update.sh                  
Cannot find docker-compose Standalone.
Please install it manually regarding to this doc site: https://mailcow.github.io/mailcow-dockerized-docs/i_u_m/i_u_m_install/      

actually, I was quite happy to get rid of it, and not really fond of installing a binary by downloading it somewhere and not having it under package control.

Can someone explain the rationale of requiring the standalone docker-compose again?

Thanks!

Hi!
Same here. The question for me is not so much why update.sh seems to require docker-compose but how I can make update.sh work with docker compose. Am I missing something?
Greetings,
Andreas

Have something to say?

Join the community by quickly registering to participate in this discussion. We'd like to see you joining our great moo-community!

  • MAGIC

    • Forum Staff
    • volunteer
    Moolevel 48

Sorry for the hassle with it. Devs decided to move to docker-compose again because there were lot issues regarding upgrading and so on with docker compose.
Of course you can install docker compose via your repos as long as its newer than the recommended version (2.6.1)

Hi! Of course I support the devs’ decisions and it’s not that I didn’t ever have to take a step back. It would just have been great to be informed by a blog post, like “if you have already moved to docker compose, here’s what you have to do…”
But again, stuff happens and the problem is solved for now, everything’s cool. Maybe in the future…?

No one is typing