8000 `docker compose logs` not working · Issue #1299 · abiosoft/colima · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

docker compose logs not working #1299

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

Closed
1 of 5 tasks
chuntangwang opened this issue Apr 9, 2025 · 1 comment
Closed
1 of 5 tasks

docker compose logs not working #1299

chuntangwang opened this issue Apr 9, 2025 · 1 comment

Comments

@chuntangwang
Copy link

Description

docker compose logs can't show any logs, but docker logs works.

Try to print --verbose or debug mode showing below info, not sure it is relative.

❯ docker compose --verbose logs -f container_name
TRAC[0000] Docker Desktop integration not enabled
DEBU[0000] otel error                                    error="<nil>"
DEBU[0000] otel error                                    error="<nil>"

❯ docker -D compose logs
DEBU[0000] otel error                                    error="<nil>"
DEBU[0000] otel error                                    error="<nil>"

Version

colima version HEAD-9d0de69
git commit: 9d0de69a37f437e75110b7a85c4c9012f4fa99c1

runtime: docker
arch: aarch64
client: v28.0.4
server: v28.0.4

Operating System

  • macOS Intel <= 13 (Ventura)
  • macOS Intel >= 14 (Sonoma)
  • Apple Silicon <= 13 (Ventura)
  • Apple Silicon >= 14 (Sonoma)
  • Linux

Output of colima status

INFO[0000] colima is running using macOS Virtualization.Framework
INFO[0000] arch: aarch64
INFO[0000] runtime: docker
INFO[0000] mountType: virtiofs
INFO[0000] socket: unix:///Users/user/.colima/default/docker.sock

Reproduction Steps

  1. docker compose -p dev up -d
  2. docker compose --verbose logs -f container_name

Expected behaviour

docker compose logs should print logs.

Additional context

No response

@chuntangwang
Copy link
Author

It's my mistake the docker compose commands.
I should also add --project-name or -p with docker compose logs, docker compose ps, etc after using docker compose -p dev up -d.

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

No branches or pull requests

1 participant
0