You can do this, or upgrade docker compose to the latest version. It works because you can pass the service names after the “ps” subcommand. If you just want to see the list of services defined in a specific compose file, you can use the config subcommand instead of ps docker compose -f config -servicesīased on that if you need the status of those services, the actual workaround would be something like this: docker-compose -f ps $(docker-compose -f config -services) I also have to agree with that using the project name would be the correct way in case of docker compose up, but if you just want to see the state of some services in a specific compose file belonging to the only one project you have, this bug can be a problem. I downloaded that version to my Mac and saw the same issue. Okay I can confirm, this seems to be a bug in Docker Compose v2.6. In image 6.0 docker-compose is upgraded to 2.6.0 from 1.26.0 in image 4.0. NOTE - I started seeing this problem only after moving to aws/codebuild/standard image 6.0 from 4.0. I am executing docker-compose like below docker-compose -compatibility -f docker-compose.yml up -scale es01=0 -scale elasticsearch-mapping-init=0 -scale analytics-db=0ĭocker-compose -compatibility -f up -scale autocomplete-service=0Īfter this when I am executing the below command it is displaying all services not just the ones defined in docker-compose -f ps -servicesĭ has only the below services version: '3'Ĭan someone let me know why docker-compose -f ps -services not listing the services defined in only? Cross-posting from stackoverflow as I did not get any response there.
0 kommentar(er)
