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
I started encountering errors with docker/build-push-action@v5 today since v5.4.0 was released. Since it was on a minor version the error was unexpected. This is the message I see for the action step failure:
ERROR: docker exporter does not currently support exporting manifest lists
Error: buildx failed with: ERROR: docker exporter does not currently support exporting manifest lists
Downgrading and locking the action to docker/build-push-action@v5.3.0 helps avoid any errors in the short term.
It's likely that I'm doing something wrong with the action setup. I don't understand what the error means with how I'm using the action. I believe the error may be related to this change. Could the error have to do with using a self-hosted runner?
Contributing guidelines
I've found a bug, and:
Description
I started encountering errors with
docker/build-push-action@v5
today since v5.4.0 was released. Since it was on a minor version the error was unexpected. This is the message I see for the action step failure:Downgrading and locking the action to
docker/build-push-action@v5.3.0
helps avoid any errors in the short term.It's likely that I'm doing something wrong with the action setup. I don't understand what the error means with how I'm using the action. I believe the error may be related to this change. Could the error have to do with using a self-hosted runner?
Example action setup:
Expected behaviour
No errors on a minor version (v5.4.0) update.
Actual behaviour
The v5.4.0 action fails to run with an error message as noted in the description. It's likely user error though.
Repository URL
No response
Workflow run URL
No response
YAML workflow
Workflow logs
No response
BuildKit logs
No response
Additional info
No response
The text was updated successfully, but these errors were encountered: