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

Update Debian Version to Resolve GLIBC Compatibility Issue #156

Merged
merged 3 commits into from
Aug 9, 2023

Conversation

Krishnacore
Copy link
Contributor

Description of Changes

Currently, the image is being built using the rust:latest base image, which is based on debian:bullseye, where:

ldd --version
ldd (Debian GLIBC 2.31-13+deb11u6) 2.31

Then, the final binary is placed in the debian:buster image, where version is:

ldd --version
ldd (Debian GLIBC 2.28-10+deb10u2) 2.28

This leads to an error during application startup, due to a missing GLIBC_2.29 version, as shown below:

magi: /lib/aarch64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by magi)

To resolve this issue and ensure library compatibility, it's recommended to use the same Debian version for both images. In this case, it's proposed to switch from debian:buster-slim to debian:bullseye-slim.

Changes in Dockerfile

-FROM debian:buster-slim
+FROM debian:bullseye-slim

@Krishnacore
Copy link
Contributor Author

Also updated ether version and fixed broken links for downloading archives

Copy link
Contributor

@ncitron ncitron left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! I'll cut a new release and push to docker hub now.

@ncitron
Copy link
Contributor

ncitron commented Aug 9, 2023

Everything seems to be working well. New images are up on docker hub at a16zcrypto/magi.

Thanks for the help here!

@ncitron ncitron merged commit 2d61a88 into a16z:master Aug 9, 2023
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants