rtk-ai/rtk

docker logs summarization hides progress bars and streaming output

Open

#1.267 aberto em 13 de abr. de 2026

Ver no GitHub
 (1 comment) (0 reactions) (0 assignees)Rust (2.914 forks)batch import
area:clibugeffort-mediumenhancementfilter-qualityhelp wantedplatform:linuxpriority:medium

Métricas do repositório

Stars
 (48.085 stars)
Métricas de merge de PR
 (Mesclagem média 11d 1h) (45 fundiu PRs em 30d)

Description

What's happening

When running rtk docker logs <container>, the output gets summarized into a "Log Summary" block instead of showing the actual log lines:

[docker] Logs for truckfull-nominatim:
Log Summary
   [error] 0 errors (0 unique)
   [warn] 0 warnings (0 unique)
   [info] 0 info messages

Meanwhile, running docker logs <container> directly shows the actual output — import progress, phase changes, node counts, etc.

Why it's a problem

I was importing a 3.8GB Nominatim PBF file into a Docker container and needed to monitor progress. The actual container was printing Processing: Node(538363k 15... type progress lines, but rtk docker logs just showed "0 errors, 0 warnings, 0 info messages" — which made it look like nothing was happening.

I ended up having to open a second terminal and run docker logs directly to see what was going on. Kind of defeats the purpose of having rtk wrap the command.

What I'd expect

Some way to get the raw output when I need it. A couple ideas:

  1. --raw flag on rtk docker logs that passes output through unmodified
  2. Smarter summarization that recognizes progress-style output (lines with \r, percentages, counters) and passes those through instead of collapsing them
  3. Config option to disable log summarization entirely for specific containers or commands

The token savings are great most of the time, but for long-running processes where I'm actively watching progress, I need to see the actual output.

Environment

  • rtk 0.35.0
  • Ubuntu, Linux
  • Using rtk as a shell hook with OpenCode

Guia do colaborador