docker / docker/buildx

isolate rawjson output from other status/error messages

Open
#2,967 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

kind/enhancement status/triage
Dominant language
Go
Stars
4.5k
Forks
682
Avg merge
2d 14h
Merged PRs (30d)
29

Description

Description

when ran with --progress=rawjson buildx/bake sends json events on stderr, which get mixed with warnings (fixed by https://github.com/docker/buildx/pull/2957) and errors, which can confuse a json parser used by consumer.
Would be nice there's an option to switch the json stream on stdout, maybe based on some env variable ?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing how buildx/bake handles --progress=rawjson and routes its JSON events, then inspect the existing separation from warnings mentioned in pull request #2957. The work is complete when a supported option, potentially an environment variable, keeps the JSON stream on stdout without errors contaminating it.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, go
Domain
cli
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.