CrazyMax

Maybe we could add a `level` attribute to log config https://github.com/moby/buildkit/blob/15b43c86133070a488ee44f868a576ebcb7fe4b8/cmd/buildkitd/config/config.go#L57-L59 And deprecate `debug` and `trace` attributes. We might keep `--debug` and `--trace` flags as shorthand for `--log-level` flag.

Thanks for this report, will take a closer look and come back to you.

Yes that makes sense to fallback to GH API or GH cdn with higher rate limit of 5000req/h. I will take a look

> -H "Markdown: yes" Do you have link to the documentation about it please?

> One uses `SOURCE_DATE_EPOCH` as follows: > > ``` > $ SOURCE_DATE_EPOCH=0 docker buildx bake > $ SOURCE_DATE_EPOCH=42 docker buildx bake > ``` > > Does this PR support this...

> Maybe I was not clear enough in #3197: > > ``` > $ SOURCE_DATE_EPOCH=0 docker buildx bake > ``` > > ```hcl > labels = { > "org.opencontainers.image.created" =...

> _(looks like github skipped my main review message, reposing in case it doesn't appear)_ > > Still somewhat confused about this. > > * what is the use case...

Can you give a minimal repro with Dockerfile(s) and Compose file? Also what's the output of `docker info`

@ndeloof Don't have perms to transfer @nocive Do you have a minimal repro? Can you also show the output of `docker buildx inspect`?

Ok it seems we have an issue when exporting build records with kubernetes driver: https://github.com/docker/buildx/actions/runs/16618088830/job/47015660807?pr=3344#step:9:321 ``` + docker buildx --builder=buildx-test-81a84e3206624d8ccfa87d0671c83caf history ls }BUILD ID NAME STATUS CREATED AT DURATION b3lghrsw4kokqcu6o9noohf5r...