Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docker-compose is always used instead of docker compose #149

Closed
entr opened this issue May 6, 2022 · 2 comments · Fixed by #150
Closed

docker-compose is always used instead of docker compose #149

entr opened this issue May 6, 2022 · 2 comments · Fixed by #150
Labels

Comments

@entr
Copy link

entr commented May 6, 2022

I have both docker-compose and docker compose commands available in Terminal (idk if this is normal). I'm running docker on Apple M1. Docker is installed using brew as a cask. During my debugging efforts on different issues, I noticed that docker-compose is always used instead of docker compose.

$ DIP_ENV=debug dip up -d

[{ __REDACTED__ }, "docker inspect --format '{{ .NetworkSettings.Networks.frontend.IPAddress }}' dnsdock"]
[{ __REDACTED__ }, "docker compose version"]
[{ __REDACTED__ }, "docker-compose --file path-to-my-project/docker/compose.yml --project-name my-project-name up -d

If I run docker compose version manually in the Terminal:

$ docker compose version
Docker Compose version v2.4.1

Context:

  • OS: MacOS Monterey 12.0
  • Shell: zsh 5.8 (x86_64-apple-darwin21.0)
  • Ruby: ruby 2.6.3p62 (2019-04-16 revision 67580) [universal.arm64e-darwin21]
  • dip: 7.3

Let me know if you need anything else from me and thanks for the great tool!

@bibendi
Copy link
Owner

bibendi commented May 7, 2022

Hi!
Wierd! I have no idea why this happens :( I'll try to debug this next week.

@bibendi
Copy link
Owner

bibendi commented May 7, 2022

It turned out the fix was pretty simple.
I've released the 7.3.1 version.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants