[GitHub] [apisix-ingress-controller] zaunist commented on issue #1201: bug: Discuss how to face the docker compose update

[GitBox <gi...@apache.org>]

zaunist commented on issue #1201:
URL: https://github.com/apache/apisix-ingress-controller/issues/1201#issuecomment-1202188720

   > First, I have installed Docker Compose!
   > 
   > @AlinsRan Maybe I didn't express myself clearly. What I meant was that the latest version of docker compose executes the command `docker compose` instead of `docker-compose`. So do we have to improve the makefile to accommodate this change. Or does anyone have a better suggestion?
   
   Hello, @Chever-John. 
   
   I went through the [Docker documentation](https://docs.docker.com/compose/) and noticed the following passage
   
   > Run docker compose up and the [Docker compose command](https://docs.docker.com/compose/#compose-v2-and-the-new-docker-compose-command) starts and runs your entire app. You can alternatively run docker-compose up using Compose standalone(docker-compose binary).
   
   I think the problem here is that the new version of docker integrates the `compose` command and you are trying to use the new way, but docker also supports the old version of `docker-compose`. considering the compatibility with the old version, I think it is better to keep the current approach.
   
   Feel free to point out if I'm wrong in my description.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org