CrazyMax

@Frederik-Baetens From what I see you're running the Docker daemon as a non-root user (rootless mode). In that case I think you should use the rootless buildkit image: ```yaml -...

@jamesdh Thanks for your report. Remove `version: latest` and `buildkitd-flags: --debug` from `Build and push` step. These inputs are [not valid for this action](https://github.com/docker/build-push-action/#inputs) but [valid for `docker/setup-buildx-action`](https://github.com/docker/setup-buildx-action#inputs). Also can...

@jamesdh Have you tried with [my suggestion](https://github.com/docker/build-push-action/issues/259#issuecomment-748501630)? Do you have a link to your repo for repro please?

@jamesdh > `# cache-to: type=registry,ref=ghcr.io/moltenbits/tt-grails,mode=max` Fyi, `mode=max` is quite aggressive. Caches for all stages of your Dockerfile will be pushed. > Yea, I added those flags but it didn't appear...

Looks similar to https://github.com/moby/buildkit/issues/2888

> Is this an expected behaviour? No and it seems to be happening quite recently. Wonder if something has changed with GitHub. > In our case, should we just be...

Tracked in https://github.com/docker/roadmap/issues/269

@efernandesng I think this example should be in the buildx repo instead: https://github.com/docker/buildx/blob/master/docs/reference/buildx_build.md#secret

We will work on this. Keep you in touch! (cc @technicallyjosh) @lirantal Some changes may be required to allow a PAT to modify the README on Docker Hub. ATM only...

@MarcelCoding > The cache can grow very quickly with large images, since old entries are not deleted. Yes you're right atm caches are copied over the existing cache so it...