You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In Alpine 3.17, Openssl is 3 by default, so those images are already using it (and the reason for 2.7 and 3.0 not having Alpine 3.17 images). See #392.
As far as the Debian based images, that will happen in the Debian Bookworm based images, but Bookworm is not a stable release yet, so we don't base any images on it.
Hey @yosifkit sorry if this is better answered elsewhere, but what's the timeline for starting to produce bookworm images across the Official Images portfolio?
Per the bookworm Freeze Timeline and Policy page, bookworm is planned enter "hard freeze" in less than a month. Will there be some lead time before bookworm is actually released when we can start testing the image updates, such as after the hard freeze or the full freeze?
Ideally, we prefer to wait until actual release (and will definitely do so for generic aliases like latest, etc), but if there are sufficiently compelling reasons we have added new variants earlier -- each level of freeze usually requires an inversely proportional level of compelling reasoning. 😅
This broke our application. We used the image ruby:3.2.2 and suddenly it changed from bullseye to bookworm. Do we have to reckon with operating system version changes in the future?
Any image tag that doesn't pick an OS release, like ruby:3.2.2 is subject to an OS release update when the next stable release of the distribution comes out. A tag with a Debian release name (or Alpine version) will stay on that release, like ruby:3.2.2-bullseye (or ruby:3.2.2-alpine3.17). We support and build images for the two latest stable releases of each distribution, so Debian Bookworm and Bullseye and Alpine 3.18 and 3.17.
I want to use ruby:3.2.2-slim-bookworm, but get OpenSSL is not available. Install OpenSSL and rebuild Ruby or use non-HTTPS sources (Gem::Exception). How to fix this issue? Do I have to stay on bullseye, or which image do you recommend?
Hey @LaurentGoderre,
thank you for the response. Here's my Dockerfile:
# syntax=docker/dockerfile:1ARG RUBY_VERSION
ARG DISTRO_NAME=bookworm
# RUBY_VERSION has to be defined in docker-compose.ymlFROM ruby:$RUBY_VERSION-slim-$DISTRO_NAME AS development
ARG PG_MAJOR
ARG DISTRO_NAME
ARG USER_ID
ARG GROUP_ID
ENV TZ="Europe/Vienna"# Common dependenciesRUN --mount=type=cache,target=/var/cache/apt,sharing=locked \
--mount=type=cache,target=/var/lib/apt,sharing=locked \
--mount=type=tmpfs,target=/var/log \
rm -f /etc/apt/apt.conf.d/docker-clean; \
echo 'Binary::apt::APT::Keep-Downloaded-Packages "true";' > /etc/apt/apt.conf.d/keep-cache; \
apt-get update -qq \
&& DEBIAN_FRONTEND=noninteractive apt-get install -yq --no-install-recommends \
build-essential \
gnupg2 \
curl \
less \
git
RUN addgroup --gid $GROUP_ID user
RUN adduser --disabled-password --gecos '' --uid $USER_ID --gid $GROUP_ID user
# Configure bundlerENV LANG=C.UTF-8 \
BUNDLE_JOBS=4 \
BUNDLE_RETRY=3
# Uncomment this line if you store Bundler settings in the project's rootENV BUNDLE_APP_CONFIG=.bundle
# Uncomment this line if you want to run binstubs without prefixing with `bin/` or `bundle exec`# ENV PATH /app/bin:$PATH# Create a directory for the app codeRUN mkdir -p /home/user/app
RUN chown -R user:user /home/user/app
USER user
# Upgrade RubyGems and install required Bundler versionRUN gem update && \
gem install bundler
WORKDIR /home/user/app
Just to resummarize our position here, we're maintaining builds of upstream-supported versions of Ruby against up to two distributions for upstream-supported combinations, which means that Ruby 3.0 will unfortunately not be getting any further distribution updates beyond Alpine 3.16 and Debian Bullseye (because of OpenSSL 3). However, it is EOL in ~3 months (Mar 2024), so I'd suggest any users get off Ruby 3.0 ASAP.
Activity
yosifkit commentedon Dec 19, 2022
In Alpine 3.17, Openssl is 3 by default, so those images are already using it (and the reason for
2.7and3.0not having Alpine 3.17 images). See #392.As far as the Debian based images, that will happen in the Debian Bookworm based images, but Bookworm is not a stable release yet, so we don't base any images on it.
md5 commentedon Feb 20, 2023
Hey @yosifkit sorry if this is better answered elsewhere, but what's the timeline for starting to produce
bookwormimages across the Official Images portfolio?Per the bookworm Freeze Timeline and Policy page,
bookwormis planned enter "hard freeze" in less than a month. Will there be some lead time beforebookwormis actually released when we can start testing the image updates, such as after the hard freeze or the full freeze?tianon commentedon Feb 22, 2023
Ideally, we prefer to wait until actual release (and will definitely do so for generic aliases like
latest, etc), but if there are sufficiently compelling reasons we have added new variants earlier -- each level of freeze usually requires an inversely proportional level of compelling reasoning. 😅lzettel commentedon Jun 21, 2023
This broke our application. We used the image ruby:3.2.2 and suddenly it changed from bullseye to bookworm. Do we have to reckon with operating system version changes in the future?
yosifkit commentedon Jun 21, 2023
Any image tag that doesn't pick an OS release, like
ruby:3.2.2is subject to an OS release update when the next stable release of the distribution comes out. A tag with a Debian release name (or Alpine version) will stay on that release, likeruby:3.2.2-bullseye(orruby:3.2.2-alpine3.17). We support and build images for the two latest stable releases of each distribution, so Debian Bookworm and Bullseye and Alpine 3.18 and 3.17.wuarmin commentedon Oct 30, 2023
I want to use
ruby:3.2.2-slim-bookworm, but getOpenSSL is not available. Install OpenSSL and rebuild Ruby or use non-HTTPS sources (Gem::Exception). How to fix this issue? Do I have to stay onbullseye, or which image do you recommend?Thanks
LaurentGoderre commentedon Oct 30, 2023
@wuarmin I just tried and it worked for me. What were you running?
wuarmin commentedon Oct 31, 2023
Hey @LaurentGoderre,
thank you for the response. Here's my Dockerfile:
and docker-compose.yml:
After the runner is built
following command inside the container:
fails with:
wuarmin commentedon Nov 13, 2023
@LaurentGoderre Do you have an idea?
LaurentGoderre commentedon Nov 13, 2023
Strange I used your code and it worked for me
LaurentGoderre commentedon Nov 13, 2023
Oh, I did have to comment out the
bashrcmount into the container and I wonder if something in there could be throwing it offtianon commentedon Dec 19, 2023
Just to resummarize our position here, we're maintaining builds of upstream-supported versions of Ruby against up to two distributions for upstream-supported combinations, which means that Ruby 3.0 will unfortunately not be getting any further distribution updates beyond Alpine 3.16 and Debian Bullseye (because of OpenSSL 3). However, it is EOL in ~3 months (Mar 2024), so I'd suggest any users get off Ruby 3.0 ASAP.