You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The documentation does not mention anything about my problem
There are no open or closed issues that are related to my problem
Description
When trying to use this Action @v6 with the latest Docker Buildx 0.20.0, the --cache-from directive causes an error.
We are using a CSV list of values for cache-from which appear to get squashed together on a single --cache-from CSV. Whereas, the tag values are separated into separate --tag.
Expected behaviour
Buildx action builds with arguments properly.
Actual behaviour
Error: buildx failed with: ERROR: invalid value <REDACTED>.dkr.ecr.us-gov-west-1.amazonaws.com/app:git-000
farvour
changed the title
Action v6 isn't compatible with latest docker buildx 0.20.0
Action v6 using --cache-from isn't compatible with latest docker buildx 0.20.0
Jan 21, 2025
This might be related but without logs it's hard to figure out. Can you post the full logs of the Build, tag and push image to ECR - stage1 step please?
We are using a CSV list of values for cache-from which appear to get squashed together on a single --cache-from CSV
Added tests in docker/build-push-action#1307 and can't repro. If you have a link to a repository with small repro or workflow logs that would help. Closing in the meantime.
Contributing guidelines
I've found a bug, and:
Description
When trying to use this Action
@v6
with the latest Docker Buildx 0.20.0, the--cache-from
directive causes an error.We are using a CSV list of values for
cache-from
which appear to get squashed together on a single--cache-from
CSV. Whereas, the tag values are separated into separate--tag
.Expected behaviour
Buildx action builds with arguments properly.
Actual behaviour
Repository URL
No response
Workflow run URL
No response
YAML workflow
Workflow logs
No response
BuildKit logs
Additional info
Is it related to this? #2814
The text was updated successfully, but these errors were encountered: