PR opened docker/buildx
Move a paragraph in README to clarify where it fits in the structure.
-
Before the move, the paragraph seems to apply to the
--output=localsection when in fact it applies to the entire--outputsection. This is especially confusing for the sentence "if just the path is specified as a value,buildxwill use the local exporter with this path as the destination". -
After the move, it is clear that the paragraph applies to
--output
pr created time in 6 days
push eventshykes/buildx
commit sha d7adb9ef6e8d89e4f2e4214609acd1859141eb38
Clarify documentation structure Move a paragraph in README to clarify where it fits in the structure. - Before the move, the paragraph seems to apply to the `--output=local` section when in fact it applies to the entire `--output` section. This is especially confusing for the sentence "if just the path is specified as a value, `buildx` will use the local exporter with this path as the destination". - After the move, it is clear that the paragraph applies to `--output`
push time in 6 days
issue commentdocker/buildx
I agree --progress=json is better. Thanks.
comment created time in 18 days
issue openeddocker/buildx
It would be awesome if buildx <bake|build> supported --progress=raw, which would output a json stream with all the structured status information, to pipe into custom progress display helpers without having to patch buildx itself.
My understanding based on Tibor's explanation is that the internal plumbing is already in place for accessing the structured status info, it's just that right now it requires linking against buildkit itself.
created time in 19 days
startedstreamlit/streamlit
started time in 2 months
startedcuelang/cue
started time in 2 months