Justin Chadwell
Justin Chadwell
I found this and tried to fix this as part of https://github.com/dagger/dagger/issues/7954, but I don't actually think the issue is related.
For `buildx ls`, we should follow similar conventions to `buildx inspect`. i.e. the following should be the same: ``` $ docker buildx inspect desktop-linux Name: desktop-linux Driver: docker Nodes: Name:...
Can you explain the logic for this? The original reasoning for sending interrupt signals for processes is that we want to ensure that the process has terminated for the test...
> These commands are running in foreground, and run to completion, so I thought it should be ok to not have a cleanup function for it. They *should* run to...
cc @helderco @shykes (you're probably the right people to look at this one)
Since you've redacted the ``, we can't tell where this error comes from - the 400 is coming from the registry, but it's not clear why. I assume it's a...
@pimvandenbroek do you have log messages from the push to GCR? We've been successfully pushing the new provenance attestations to GCR without too much of a problem :eyes:
@pimvandenbroek I think this is unrelated to this issue, looks like https://github.com/moby/buildkit/pull/2982/commits/c5242ba8fba75baccac5140236c057357163d903 is the source of the error message that was introduced in the newest BuildKit. I think this is...
I split some work out to #10058, so will rebase on that once merged.
@gerhard I've added some tests for some of the particularly tricky bits.