-
Notifications
You must be signed in to change notification settings - Fork 987
Docker buildx component missing in standard:7.0
#625
New issue
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
Comments
standard-7.0
standard:7.0
@Dylan-AWS Can you check this? |
We will look to include this on the next image release expected to be middle of May. |
@SunsetYe66
|
@Niknu BTW, standard images straightforwardly download and decompress Docker files and does not used APT. There might be some possibility with your way to temporarily workaround this issue. |
@SunsetYe66 , |
It's also missing in By default I get this deprecation warning when running
If I set
|
I think the fix is broken. Docker buildx binary also need to be located under /usr/local/lib/docker/cli-plugins I tested in our account and with latest standard:7.0 version:
|
Literally tried to use this earlier today and encountered exactly what is stated above. Any update on the fix? |
This is accurate. The buildx plugin will be installed in the correct location with the next release. In the meantime, buildx is currently installed in As a temporary workaround, you may be able to use buildx by either -
Example buildspec -
|
Did this get fixed? We had to implement this symlink workaround for 7.0 image. However, that workaround failed today because "file already exists" which suggests that it has been fixed. @Antonio-AWS can we get a confirmation? |
Fixed in latest release: 182bbfd#diff-c1ea454e65b48efad7d52406144e50f8459244517f0eb25a5ec3da4f865a3129 |
Wondering why is this not included in amazonlinux2-aarch64? |
@Antonio-AWS When will the amazonlinux2-aarch64 Image be fixed? #640 |
Uh oh!
There was an error while loading. Please reload this page.
Describe the bug
A clear and concise description of what the bug is.
Refers to Docker release note:
This will result in Dockerfile stated BUILDKIT=1 to fail.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
This will success in both standard:6.0 and 5.0
Logs
N/A
Platform (please complete the following information):
N/A
Additional context
N/A
The text was updated successfully, but these errors were encountered: