Without this, RVM downloads a binary Ruby with a bunch of configuration
options turned on. This can lead to problems building extensions when
Ruby thinks a certain feature is supported but our Docker image doesn't
have the headers to support it. Right now we're seeing that in the zlib
gem: it has extra code to turn on when Ruby supports Valgrind, but we
don't have the Valgrind headers necessary to build that code.
Closes #21028.
Arvados-DCO-1.1-Signed-off-by: Brett Smith <brett.smith@curii.com>
RUN gpg --import --no-tty /tmp/mpapis.asc && \
gpg --import --no-tty /tmp/pkuczynski.asc && \
curl -L https://get.rvm.io | bash -s stable && \
- /usr/local/rvm/bin/rvm install 2.7 -j $(grep -c processor /proc/cpuinfo) && \
+ /usr/local/rvm/bin/rvm install --disable-binary 2.7 -j $(grep -c processor /proc/cpuinfo) && \
/usr/local/rvm/bin/rvm alias create default ruby-2.7 && \
echo "gem: --no-document" >> ~/.gemrc && \
/usr/local/rvm/bin/rvm-exec default gem install bundler --version 2.2.19 && \