CrazyMax

Results 1192 comments of CrazyMax

@MarcelCoding > that means that the cache-to option does not export the entire Docker cache, just the one for the current images? [`cache-to`](https://github.com/docker/buildx#--cache-tonametypetypekeyvalue) exports the build cache for the current...

@jauderho https://github.com/docker/build-push-action/blob/master/docs/advanced/cache.md#github-cache

You can test the gha cache exporter using [this workflow](https://github.com/docker/build-push-action/pull/406#issuecomment-879184394) while waiting for buildx 0.6 and BuildKit 0.9 to be GA. Feel free to give us your feedback, thanks!

@jauderho > Looks like the "Setup Buildx" step now takes longer but I'm assuming that's due to the rest not yet being merged in. More importantly, the "Build and push"...

@jauderho > Looks like the "Setup Buildx" step now takes longer Buildx [0.6.0-rc1](https://github.com/docker/buildx/releases/tag/v0.6.0-rc1) has been released. I've updated [the workflow](https://github.com/docker/build-push-action/pull/406#issuecomment-879184394) to use it so now it should be faster than...

@jauderho Use `image=moby/buildkit:master` instead of `image=moby/buildkit:v0.9.0-rc1`.

@jauderho As you're on a monorepo building multi Docker images with different context, you should use a specific `scope` for each one of them to avoid cache collision/invalidation. For example...

@jauderho [GitHub virtual environments](https://github.com/actions/virtual-environments) don't have buildx 0.6.0 ([0.5.1 atm](https://github.com/docker/build-push-action/runs/3096831142?check_suite_focus=true#step:5:4)) so you have to explicitly specify buildx version in your workflow. On the other hand [BuildKit default image](https://github.com/docker/buildx/blob/ab09846df70df822fd32b9d0c715dc0605344618/driver/bkimage/bkimage.go#L4) is up...

> works great. this can be closed probably This issue is about the `local` cache so we keep it opened until moby/buildkit#1896 is fixed. Thanks.

@roim Do you have a link to your repo for repro please? You can use the [Path context](https://github.com/docker/build-push-action#path-context) (with checkout action) in the meantime.