-
Notifications
You must be signed in to change notification settings - Fork 5.2k
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
V2:docker compose ps command and docker-compose ps command get content not the same #9705
Comments
Hello @kerwinLV |
so your mean it's the correct output? right? kind of confuse, I want the output is isolated every yaml manage one each other compose |
Ahh, it doesn't. I'll see if I can make some changes to #9375 to apply the same logic to |
This is another service YAML file, I wish this can help find the real issue
|
Oh, By the way, compose v2 can't via press TAB auto-completion. It kind of impacts user experience, ahh but it's' no big deal, don't put it on your mind, have a good day. |
Compose V2 restart command have same problem |
docker compose -f ./ProcessFile/AIServer/yaml/AIServer.yaml logs command have same problem,hi @laurazard ,I didn't see Compose v2.10.2 fix it.please, thanks a lot. |
When using the file model, only attach to services referenced in the active Compose file. For example, let's say you have `compose-base.yaml` and `compose.yaml`, where the former only has a subset of the services but are both run as part of the same named project. Project based command: ``` docker compose -p myproj logs ``` This should return logs for active services based on the project name, regardless of Compose file state on disk. File based command: ``` docker compose --file compose-base.yaml logs ``` This should return logs for ONLY services that are defined in `compose-base.yaml`. Any other services are considered 'orphaned' within the context of the command and should be ignored. See also docker#9705. Fixes docker#9801. Signed-off-by: Milas Bowman <milas.bowman@docker.com>
* logs: filter to services from current Compose file When using the file model, only attach to services referenced in the active Compose file. For example, let's say you have `compose-base.yaml` and `compose.yaml`, where the former only has a subset of the services but are both run as part of the same named project. Project based command: ``` docker compose -p myproj logs ``` This should return logs for active services based on the project name, regardless of Compose file state on disk. File based command: ``` docker compose --file compose-base.yaml logs ``` This should return logs for ONLY services that are defined in `compose-base.yaml`. Any other services are considered 'orphaned' within the context of the command and should be ignored. See also #9705. Fixes #9801. Signed-off-by: Milas Bowman <milas.bowman@docker.com>
Description
Steps to reproduce the issue:
1.docker compose -f /home/kerwin/process_file/test_fastapi_v2_update/yaml/test_fastapi_v2_update.yaml ps
2.docker-compose -f /home/kerwin/process_file/test_fastapi_v2_update/yaml/test_fastapi_v2_update.yaml ps
3.
Describe the results you received:
output of
docker compose
Describe the results you expected:
output of
docker-compose
Additional information you deem important (e.g. issue happens only occasionally):
Compose file:
Output of
docker compose version
:Docker Compose version v2.6.0
Output of
docker info
:Additional environment details:
ubuntu-22.04
The text was updated successfully, but these errors were encountered: