Latest update breaking ruby 2.1.9 and mysql #2014
Replies: 2 comments 5 replies
-
|
Could you provide a Dockerfile to reproduce this? 2.1.* is long EOL and unsupported, so if this turns out to be an issue in CRuby there is no chance to fix it. The |
Beta Was this translation helpful? Give feedback.
-
|
Yes, unfortunately this project is an old one and we have yet to upgrade to the latest version of ruby on rails |
Beta Was this translation helpful? Give feedback.
-
|
This works for me locally (it prints Mysql2): FROM ubuntu:18.04 as base
ENV TZ=America/Los_Angeles
ENV DEBIAN_FRONTEND=noninteractive
ENV PATH="/root/.rbenv/shims:/root/.rbenv/bin:$PATH"
ENV RUBY_CONFIGURE_OPTS="--disable-install-doc --with-jemalloc"
ENV RBENV_VERSION=2.1.9
ENV BUNDLER_VERSION=1.17.3
RUN apt-get update -qq && apt-get install -y libjemalloc-dev && rm -rf /var/lib/apt/lists/*
ENV LD_PRELOAD=/usr/lib/x86_64-linux-gnu/libjemalloc.so.1
RUN ln -snf /usr/share/zoneinfo/$TZ /etc/localtime \
&& echo $TZ > /etc/timezone \
&& apt-get update -qq \
&& apt-get install -y --no-install-recommends \
ca-certificates \
gnupg2 \
autoconf \
bison \
build-essential \
git \
libcups2-dev \
libffi-dev \
libgdbm-dev \
libncurses5-dev \
libreadline-dev \
libssl1.0-dev \
libyaml-dev \
libxslt1-dev \
wget \
zlib1g-dev \
curl \
tzdata \
ntp \
&& apt-get install -y --no-install-recommends libmysqlclient-dev mysql-client
RUN git clone https://github.com/rbenv/rbenv.git ~/.rbenv \
&& echo 'export PATH="$PATH"' >> ~/.bashrc \
&& echo 'eval "$(rbenv init -)"' >> ~/.bashrc \
&& /bin/bash -c "source ~/.bashrc" \
&& echo "gem: --no-document" > ~/.gemrc
RUN git clone --branch master https://github.com/rbenv/ruby-build.git ~/.rbenv/plugins/ruby-build \
&& RUBY_CONFIGURE_OPTS="$RUBY_CONFIGURE_OPTS" rbenv install $RBENV_VERSION \
&& rbenv global $RBENV_VERSION \
&& gem install bundler -v $BUNDLER_VERSION
WORKDIR /app
# COPY vendor/cache ./vendor/cache
# COPY Gemfile Gemfile.lock ./
COPY Gemfile ./
RUN bundle install
FROM base as builder
RUN MYSQL_ADAPTER=nulldb bundle exec ruby -rmysql2 -e 'p Mysql2'I would suggest to clean and repopulate your Also you both using both Re What ultimately changed here is that openssl 1.0.2 gets compiled, even though the system has it. I will investigate why. |
Beta Was this translation helpful? Give feedback.
-
So on So the system openssl version is considered 1.1.1, and there seems to be almost nothing to tell us there is also a system openssl 1.0 installed. I'm not sure how CRuby even find the openssl 1.0 headers. As https://www.openssl.org/source/ says openssl 1.0.2 is EOL, and you are using it on a more recent system where it's not the "system default openssl". In the Dockerfile above you install So your system mysql package says I can't work with openssl 1.0 I need 1.1, |
Beta Was this translation helpful? Give feedback.
-
|
To be clear, the problem is mysql needs libssl 1.1 and ruby 2.1.9 needs libssl 1.0, so you end up loading two different openssl versions in the same process, and that typically ends in a segfault. To solve this you would need a mysql package which is compiled against libssl 1.0 e.g. from an older OS which has a default libssl 1.0 (or build it yourself), or you would need to use Ruby >= 2.4 which compiles against libssl 1.1. |
Beta Was this translation helpful? Give feedback.
-
|
Here is a minimal reproduction of this "half libssl1.0 half libssl1.1" state on Ubuntu 18.04: Fun/horrible mix of openssl versions. |
Beta Was this translation helpful? Give feedback.
-
|
v20220725 released and finds the correct openssl version in this situation. |
Beta Was this translation helpful? Give feedback.
-
Used ruby-build as part of the docker sequence commands in building a rails image. The ci was fine until July 20, where it produced the error below:
Versions
Temporary solution
Updated the command sequence w/c was part of building the image via rbenv and ruby-build
Beta Was this translation helpful? Give feedback.
All reactions