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

1.13-alpine rebuilt 10 hours ago now getting errors #41

Open
anthony-murphy-dubber opened this issue Jun 14, 2022 · 7 comments
Open

1.13-alpine rebuilt 10 hours ago now getting errors #41

anthony-murphy-dubber opened this issue Jun 14, 2022 · 7 comments

Comments

@anthony-murphy-dubber
Copy link

We have an issue where the following error in our containers:

Error relocating /app/erts-12.3.2.1/bin/beam.smp: _ZSt28__throw_bad_array_new_lengthv: symbol not found Error relocating /app/erts-12.3.2.1/bin/beam.smp: pthread_getname_np: symbol not found

We are building in a container created from image elixir:1.13-alpine and then running the artifact in a container created from image alpine:3.14. Up until yesterday this was working. When I check dockerhub the elixir:1.13-alpine image was rebuilt 10 hours ago.

I'm also seeing someone having similar issues here: https://stackoverflow.com/questions/72609505/issue-with-building-elixir-and-beam-on-alpine-linux

Is there anything we can do to address this?

@0xAX
Copy link

0xAX commented Jun 14, 2022

The same issue appeared to me in elixir:1.12-alpine image, what's the reason in general to update images with already existing tag?

@anthony-murphy-dubber
Copy link
Author

I've confirmed it's most likely coming from the latest build of erlang. If I pull the docker-elixir repo and hardcode to a previous of erlang by changing the first line of docker-elixir/1.13/alpine/Dockerfile from FROM erlang:24-alpine to FROM erlang:24.3.4.0-alpine

This gives me an image that allows builds to succeed.

@tielur
Copy link

tielur commented Jun 14, 2022

FWIW: The stackoverflow article has mentions of upgrading to alpine 3.16 resolving the issue. I tried that on our builds and it didn't seem to help

@sinhorinho
Copy link

FWIW: The stackoverflow article has mentions of upgrading to alpine 3.16 resolving the issue. I tried that on our builds and it didn't seem to help

freeze version with path 3 for example (FROM elixir:1.11.3-alpine or FROM elixir:1.13.3-alpine)

@anthony-murphy-dubber
Copy link
Author

Upgrading to Alpine 3.16 worked for me.

@nulian
Copy link

nulian commented Jun 16, 2022

If you want a more stable docker image it's better to use https://hub.docker.com/r/hexpm/elixir
That one has tags for the combination of elixir -> erlang -> linux version

@Odaeus
Copy link

Odaeus commented Aug 10, 2022

Thanks for the link to the more stable builds, I will try that! We currently have an Alpine version check in the Dockerfile that causes the build to fail if there is a mismatch between the Elixir image and Alpine version selected. Done by comparing /etc/alpine-release to a known good value.

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

No branches or pull requests

6 participants