-
Notifications
You must be signed in to change notification settings - Fork 99
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
Support alpine Docker image environment #37
Comments
I've seen this same issue building go binaries on the Some googling suggests installing |
Looked into those glibc dynamic linking workarounds and they do not seem to be working in this situation. Should I be looking into other software for lightweight Ruby software packaging and containerization, or is there interest in first party support for this? I know Hashi just released a Vagrant version packaged with AppImage so that route may work. |
I don't know what is different about the alpine linux environment and unfortunately I don't have the time to figure out how to get the packaged rubyc to work in it. You can define a Dockerfile that builds rubyc under alpine, then uses that rubyc to package your application, then copies the packaged application to a standalone image. I have added some instructions for building rubyc yourself to the README that may get you started. Since you need the same toolchain for building your own rubyc and for packaging your application with rubyc the main downside is the extra time spent building rubyc. Of course, you can store your alpine-compatible rubyc to save time. |
Sure, if the AppImage route does not work I will look at building rubyc with musl links. |
Great, thanks for the feedback, and let us know if we can improve the build instructions! |
I am trying to create a Docker image for this as it would be very useful in multi-stage builds for Ruby software or with e.g. OpenFaaS. Unfortunately, it seems to not be usable in an Alpine linux image.
A simple image file:
yields:
Note that the same error results from providing a full path to
rubyc
.Debugging the image with a statically compiled/linked goss go binary:
works correctly and proves there is some kind of incompatibility here.
The text was updated successfully, but these errors were encountered: