Pim van den Broek
Pim van den Broek
I partially agree. I'm using the provided options given by the Helm-chart, which aren't working as intended. And of course I understand it is still in beta, but that's exactly...
Issue doesn't seem to be limited to Yandex alone, I'm having the same issue with GCR. @langovoi 's solution fixed it for me
The initial error we received was: "registry cache exporter requires ref". I unfortunately don't have any other logs anymore. After applying the version pin, everything worked again.
Sure, I will check that out. The reason I replied here, is because up untill yesterday it was working fine. Then the Github Action Runner was updated, included buildx v.0.10.0,...
@crazy-max Not sure, I will have to test. You mean the following right: ``` - name: Set up Docker Buildx uses: docker/setup-buildx-action@v2 with: provenance: false ```
Clear. I'll try that block, as the buildx command is generated by code, and I currently don't have access to that part. I'll keep you posted
@crazy-max tested it, however apparently, the environment where the buildx command is generated is using an older version of buildkit and we received the following error: `buildx failed with: ERROR:...
@crazy-max Finally had the time to do a bit of a deepdive, and got the following result. docker buildx inspect returned the following: ``` pablo - Name: pablo pablo -...
@crazy-max Yes, without `cache-to` everything is running fine.
Does this mean that --cache-to isn't working in this version? Or do you perhaps know of a workaround so we can still use it?