-
Notifications
You must be signed in to change notification settings - Fork 47
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: support both v1 and v2 #393
Comments
epuertat
added a commit
that referenced
this issue
Jan 25, 2024
Fixes: #393 The main difference between docker compose v1 and v2 is that v1 commnad is `docker-compose`, while v2 is usually a split subcommand `docker compose`. Signed-off-by: Ernesto Puerta <[email protected]>
epuertat
added a commit
that referenced
this issue
Jan 25, 2024
Fixes: #393 The main difference between docker compose v1 and v2 is that v1 commnad is `docker-compose`, while v2 is usually a split subcommand `docker compose`. Signed-off-by: Ernesto Puerta <[email protected]>
epuertat
added a commit
that referenced
this issue
Jan 25, 2024
Fixes: #393 The main difference between docker compose v1 and v2 is that v1 commnad is `docker-compose`, while v2 is usually a split subcommand `docker compose`. Signed-off-by: Ernesto Puerta <[email protected]>
gbregman
pushed a commit
to gbregman/ceph-nvmeof
that referenced
this issue
Jan 30, 2024
Fixes: ceph#393 The main difference between docker compose v1 and v2 is that v1 commnad is `docker-compose`, while v2 is usually a split subcommand `docker compose`. Signed-off-by: Ernesto Puerta <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
No description provided.
The text was updated successfully, but these errors were encountered: