We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The github-actions workflow to build and publish docker image is failing with below error:
Error: buildx failed with: error: failed to solve: process "/dev/.buildkit_qemu_emulator /bin/sh -c /usr/local/bin/install-plugins.sh < plugins.txt" did not complete successfully: exit code: 255
Trigger the workflow without explicitly setting up QEMU emulator.
No response
If applicable, add screenshots to help explain your problem.
The text was updated successfully, but these errors were encountered:
As per docker/buildx#464 the qemu emulator need to setup. This is also recommended in all the examples https://github.com/docker/build-push-action which we are using to build and push docker image.
Sorry, something went wrong.
If this is for jenkins main node then no need to care about using buildx.
We can lock the jenkins mainnode to use x64.
It is not like we would ever run our Jenkins on arm64.
This was regarding building the docker image on GHA. Nothing related to jenkins. Looks like the fix is in. Closing the issue. Thanks!
Set up QEMU
48a54df
"setup-qemu action can be useful if you want to add emulation support with QEMU to be able to build against more platforms." https://github.com/docker/build-push-action opensearch-project/opensearch-ci#130 (comment)
rishabh6788
No branches or pull requests
Describe the bug
The github-actions workflow to build and publish docker image is failing with below error:
To reproduce
Trigger the workflow without explicitly setting up QEMU emulator.
Expected behavior
No response
Screenshots
If applicable, add screenshots to help explain your problem.
Host / Environment
No response
Additional context
No response
Relevant log output
No response
The text was updated successfully, but these errors were encountered: