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

Use 64bit versions of binaries #352

Closed
steren opened this issue May 3, 2019 · 3 comments · Fixed by #513
Closed

Use 64bit versions of binaries #352

steren opened this issue May 3, 2019 · 3 comments · Fixed by #513

Comments

@steren
Copy link

steren commented May 3, 2019

gVisor is not able to run 32bit binaries. distroless images are using the 32bit version of busybox, as a consequence, images created with distroless are failing on gVisor.

@chanseokoh
Copy link
Member

Hmm... I get the impression that BusyBox intentionally provides a single pre-compiled binary (for simplicity and manageability for example?) as they say

The "busybox-i686" version should run on both 32-bit and 64-bit x86 PCs

Technically we may be able to compile a 64-bit binary from source on our own, but I don't know if that is a good idea in terms of reliability and support. Maybe it doesn't matter much as a debug tool.

@abergmeier
Copy link

abergmeier commented May 31, 2019

The problem is not only gVisor. We currently encounter also #225 on our Kubernetes cluster.
Which makes the debug image (of Kaniko) to a large degree unusable.
IIUC #225 should be fixed by a 64-bit build of busybox.

@chanseokoh
Copy link
Member

Fixed by #513.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants