CrazyMax

> > > Opened https://gitlab.com/gitlab-org/container-registry/-/issues/1679 > > > > > > Has been added to next GitLab Registry 18.4 milestone. > > Merged https://gitlab.com/gitlab-org/container-registry/-/issues/1679#note_2792080377 See https://gitlab.com/gitlab-org/container-registry/-/commit/139ef50d14028f3f5a3389c5e570d1aaa3dc7e08 Added to [18.6 milestone](https://gitlab.com/groups/gitlab-org/-/milestones/124#tab-issues)

Yes sounds good

> `driver: kubernetes` Maybe an issue with the kubernetes driver, is your repo public so we can take a look at the logs?

> If you disable the summary generation, things seem fine again. I've experienced this on a Kubernetes driver agent also Yes this seems to be similar to https://github.com/docker/setup-buildx-action/issues/270, I will...

> When using `DOCKER_BUILD_EXPORT_LEGACY`, the post job cleanup continues and does not hang. But a warning is shown, as we have no docker daemon running. Which is expected as we...

I made some tests by creating a k3d cluster and building with it and exporting seems to work fine: ``` $ docker buildx create --name=kube --driver=kubernetes --driver-opt=namespace=buildkit kube $ docker...

> Hi there! We've also hit this issue in our CI environment. > > In our case, neither rolling back to `v6.16.0` (or earlier) nor setting `DOCKER_BUILD_EXPORT_LEGACY: true` prevented the...

@crimoniv Ah I was going to ask if you were on a self-hosted runner. I made some tests using a local k3s on GitHub public runners and looks good so...

> ``` > buildx: Docker Buildx (Docker Inc.) > Version: v0.18.0 > ``` @crimoniv Ah you're using Buildx 0.18.0 that doesn't support the `buildx history export` command so it always...

@jamesoneill997 @abatilo Can you check the buildx version on your side?