-
-
Notifications
You must be signed in to change notification settings - Fork 85
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
Building in Docker fails for alpine/musl #272
Comments
Ah yeah I don't support musl, it says so right in the first few lines:
I am not sure if I ever will tbh. Bluntly, it's more work to figure out how to get it working in this environment. I have heard too many tales of alpine being "different" enough to not investigate it. I'd consider PRs that support it, though. |
Hi, I had a chance to look into this. I can adjust the project to build for
But, I don't know enough about musl to understand what your platform is. The build system I use doesn't recognize it:
Would support for |
To be honest, we've just pinned the version to 0.23.10 and it works for us. So don't stress too much for now about it (at least from my perspective) It was being built on an alpine base on CircleCI. So I don't know what CPUs they use or why it comes as "unknown". |
We ran into the same problem when building a ruby:3.3.0-alpine based docker container with
This is probably caused by trying to run glibc programs in Alpine Linux that uses musl. According to the Alpine linux documentation there are multiple options to do this. We used the gcompat compatibility layer and added this to our RUN apk add gcompat This solved it for us. |
We still get an error even after adding
(that was using Docker 4.7.1 on a Mac Sonoma 14.6.1, built using |
I can't say what's going wrong without looking at your |
Hello, i also have the same error in my docker build using
here is a sample of my Dockerfile FROM ruby:3.2.2-alpine3.19
ENV BUNDLER_VERSION=2.4.19
RUN apk upgrade && apk add --no-cache --update build-base \
curl \
linux-headers \
git \
postgresql-dev \
postgresql-client \
vips \
libheif \
python3 \
gcompat
RUN gem install bundler --default -v ${BUNDLER_VERSION}
COPY Gemfile .
COPY Gemfile.lock .
RUN bundle install |
I can't get
Also, this is not related to lsegal/yard#1587, lsegal/yard#1528 because I use this in my Gemfile… gem 'commonmarker', '~> 2.0' # for markdown support in YARD
# gem 'yard', ['>= 0.9.27', '< 0.10']
# https://github.com/lsegal/yard/issues/1528
gem 'yard', github: 'ParadoxV5/yard', ref: '9e869c940859570b07b81c5eadd6070e76f6291e', branch: 'commonmarker-1.0' …and I have exactly the same setup on Github Action, the only difference is I used an Ubuntu with glibc image there. While this Alpine use mysl, so it's all because commonmarker is not available for that target. Installing So was someone successfully able to run yard + commonmarker 2.x on a musl based system?
Example of CI: https://gitlab.com/noraj/itdis/-/blob/master/.gitlab-ci.yml |
See https://doc.rust-lang.org/rustc/platform-support.html.
|
For easy cross compilation, can't you use the example provided by rb-sys https://github.com/oxidize-rb/actions/blob/main/cross-gem/readme.md ? |
This is a Ruby 3.3 (ruby:3.3.0-alpine) based image, that is simply doing a
bundle install
The text was updated successfully, but these errors were encountered: