CrazyMax

> I'm not seeing `secret-envs` documented there. Yes we could have a note for this input in https://docs.docker.com/build/ci/github-actions/secrets/

> What information in the readme of this repository explains that there are better docs somewhere else? Could that be added? * https://github.com/docker/build-push-action/blob/84ad562665bb303b549fec655d1b64f9945f3f91/README.md?plain=1#L159 * https://github.com/docker/build-push-action/blob/84ad562665bb303b549fec655d1b64f9945f3f91/README.md?plain=1#L251-L253

> https://github.com/junghans/test-actions/actions/runs/12834771076 This repo is about `setup-buildx-action` and I don't see any issue with it in this run:  Let me move this to `build-push-action`

> `sudo` executes successfully in the container. I don't think this is related to the action but your Dockerfile. Do you repro locally as well?

> As a workaround for now, is there a way to switch the GitHub action to use the default builder? Yes you can set the `docker` driver: ```yaml - name:...

> * $REPO2/jenkins/public-service-center-camera:240718_114140 > * $REPO2/jenkins/multidimensional-omof-device-mgr:240712_140444 > * $REPO2/jenkins/abmp-autoinstall-abmp-iap-application:240205_153437 Is one of these images publicly available so I can take a look at its content? Or can you show the...

We don't support semver comparison atm but I guess that could be a new field like: ```yaml - include_tags: - ^\d+\.\d+\.\d+$ max_tags: 5 semver: - > 1.26.0 ```

> You cannot resolve `host.docker.internal` while building with a custom builder Not sure what's your use case here. Do you want to connect to a service on the host?

> `uses: ./.github/workflows/build.yml` What this reusable workflow looks like? I guess it uses either `docker/build-push-action` or `docker/bake-action`? If that's the case then this is probably related to https://github.com/actions/download-artifact/issues/328#issuecomment-2199544827 And we...

I recall we discussed with @tonistiigi about supporting a buildkit progress for GHA. I think we could just use the [`rawjson` progress](https://docs.docker.com/reference/cli/docker/buildx/build/#progress) to handle that directly in the action instead...