Skip to content
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

Docker v1.23-latest armv8 image is built for x86_64 #22261

Closed
milkcocoa opened this issue Jul 18, 2022 · 8 comments · Fixed by #22262
Closed

Docker v1.23-latest armv8 image is built for x86_64 #22261

milkcocoa opened this issue Jul 18, 2022 · 8 comments · Fixed by #22262
Assignees
Labels
bug docker Pull requests that update Docker code
Milestone

Comments

@milkcocoa
Copy link

When I run the v1.23-latest image with my M1 MacBook Pro, I get the following error.

qemu-x86_64: Could not open '/lib64/ld-linux-x86-64.so.2': No such file or directory

Installing file command, and I investigate the envoy command with it, the binary is built for x86-64 like the following.

$ file /usr/local/bin/envoy
/usr/local/bin/envoy: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 3.2.0, BuildID[sha1]=ce49c7f65668a22b80d1e83c35d170741bb8d46a, stripped

uname command shows the image itself is the armv8 architecture.

$ uname -a
Linux b2dff1cc33b1 5.10.104-linuxkit #1 SMP PREEMPT Thu Mar 17 17:05:54 UTC 2022 aarch64 aarch64 aarch64 GNU/Linux
@milkcocoa milkcocoa added bug triage Issue requires triage labels Jul 18, 2022
@phlax
Copy link
Member

phlax commented Jul 18, 2022

@milkcocoa does doing the same thing with v1.22-latest work ?

@phlax phlax added docker Pull requests that update Docker code and removed triage Issue requires triage labels Jul 18, 2022
@phlax phlax self-assigned this Jul 18, 2022
@milkcocoa
Copy link
Author

@phlax Yes, it works.

I've just executed the file command on v1.22-latest as well.

$ file /usr/local/bin/envoy
/usr/local/bin/envoy: ELF 64-bit LSB shared object, ARM aarch64, version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux-aarch64.so.1, for GNU/Linux 3.7.0, BuildID[sha1]=c919bdec19d79e97f4f56e4095706f8e6a383f1c, stripped

@phlax
Copy link
Member

phlax commented Jul 18, 2022

cool, just wanted to see if it was a regression before tracking down - ill take a look

@milkcocoa
Copy link
Author

milkcocoa commented Jul 18, 2022

v1.23.0, and distroless v1.23-latest, and v1.23.0 have the same behavior (error).

@phlax
Copy link
Member

phlax commented Jul 18, 2022

yep problem is caused by this docker/buildx#510 bug in docker buildx

i added a default because it was breaking docs - there is a workaround in that ticket - i will PR a fix asap

phlax added a commit to phlax/envoy that referenced this issue Jul 18, 2022
@milkcocoa
Copy link
Author

Great, thanks for the quick response, and investigation.

@phlax phlax added this to the 1.23.1 milestone Jul 18, 2022
phlax added a commit that referenced this issue Jul 19, 2022
@phlax phlax reopened this Jul 25, 2022
phlax added a commit to phlax/envoy that referenced this issue Jul 28, 2022
phlax added a commit that referenced this issue Jul 29, 2022
docker: Fix/workaround docker buildx bug (#22262)

Fix #22261

Signed-off-by: Ryan Northey <[email protected]>
@phlax
Copy link
Member

phlax commented Aug 19, 2022

Fixed by #22444 i will close this once the 1.23.1 is released

matt-royal added a commit to cloudfoundry/korifi that referenced this issue Aug 19, 2022
See envoyproxy/envoy#22261 for details.

For now, v1.22-latest appears to work. v1.23-latest should work soon.
We can remove this change once there's a new contour release that
includes a fixed envoy.
matt-royal added a commit to cloudfoundry/korifi that referenced this issue Aug 22, 2022
See envoyproxy/envoy#22261 for details.

For now, v1.22-latest appears to work. v1.23-latest should work soon.
We can remove this change once there's a new contour release that
includes a fixed envoy.
matt-royal added a commit to cloudfoundry/korifi that referenced this issue Aug 22, 2022
See envoyproxy/envoy#22261 for details.

For now, v1.22-latest appears to work. v1.23-latest should work soon.
We can remove this change once there's a new contour release that
includes a fixed envoy.
@phlax
Copy link
Member

phlax commented Sep 7, 2022

fixed in version 1.23.1

@phlax phlax closed this as completed Sep 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug docker Pull requests that update Docker code
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants