Skip to content

fix: Use docker logs instead of docker compose logs#44

Merged
felipecsl merged 2 commits intomasterfrom
fix/logs-use-docker-logs
Mar 6, 2026
Merged

fix: Use docker logs instead of docker compose logs#44
felipecsl merged 2 commits intomasterfrom
fix/logs-use-docker-logs

Conversation

@felipecsl
Copy link
Owner

Summary

  • hl logs was producing no output because docker compose logs couldn't find containers — the base compose.yml only defines a template service with profiles: ["_template"], and the process-specific compose files (compose.web.yml etc.) weren't being included
  • Switched to docker logs <container_name> which targets the container directly by app name, matching the container_name set in the web compose file
  • Removed the now-unnecessary --service flag, directory checks, and compose file discovery

Test plan

  • Run hl logs -n 100 and verify output is shown
  • Run hl logs -f and verify log streaming works

🤖 Generated with Claude Code

felipecsl and others added 2 commits March 6, 2026 11:01
docker compose logs couldn't find containers because the base
compose.yml only defines a template service with profiles: ["_template"].
The actual services live in process-specific compose files (compose.web.yml
etc). Using docker logs directly with the container name is simpler and
works correctly.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@felipecsl felipecsl merged commit 9029de1 into master Mar 6, 2026
3 checks passed
@felipecsl felipecsl deleted the fix/logs-use-docker-logs branch March 6, 2026 19:04
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

Successfully merging this pull request may close these issues.

1 participant