debian bookworm

Author: tdudgeon

Dockerfile-build-debian

@@ -2,14 +2,14 @@
 # This is a heavyweight image containing all aspects of RDKit plus the build system.
 # It's purpose is to create the RDKit artifacts that will be deployed to lighter weight images.
 
-FROM debian:bullseye
+FROM debian:bookworm
 LABEL maintainer="Tim Dudgeon<[email protected]>"
 
 ARG GIT_REPO
 ARG GIT_BRANCH=master
 ARG GIT_TAG
-ARG POSTGRES_VERSION=13
-ARG BOOST_VER=1.74-dev
+ARG POSTGRES_VERSION=15
+ARG BOOST_VER=1.81-dev
 
 
 RUN apt-get update &&\
@@ -21,7 +21,7 @@ RUN apt-get update &&\
   cmake\
   sqlite3\
   libsqlite3-dev\
-  libboost-dev\
+  libboost$BOOST_VER\
   libboost-system$BOOST_VER\
   libboost-thread$BOOST_VER\
   libboost-serialization$BOOST_VER\
@@ -33,7 +33,7 @@ RUN apt-get update &&\
   libeigen3-dev\
   git\
   wget\
-  openjdk-11-jdk\
+  openjdk-17-jdk\
   postgresql-$POSTGRES_VERSION\
   postgresql-server-dev-$POSTGRES_VERSION\
   postgresql-plpython3-$POSTGRES_VERSION\
@@ -50,7 +50,7 @@ RUN git clone -b $GIT_BRANCH --single-branch $GIT_REPO &&\
 ENV RDBASE=/rdkit
 ENV LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$RDBASE/lib:$RDBASE/Code/JavaWrappers/gmwrapper:/usr/lib/x86_64-linux-gnu
 ENV PYTHONPATH=$PYTHONPATH:$RDBASE
-ENV JAVA_HOME=/usr/lib/jvm/java-11-openjdk-amd64
+ENV JAVA_HOME=/usr/lib/jvm/java-17-openjdk-amd64
 ENV CLASSPATH=$RDBASE/Code/JavaWrappers/gmwrapper/org.RDKit.jar
 
 RUN mkdir $RDBASE/build

Dockerfile-cartridge-debian

@@ -4,11 +4,11 @@
 # build the deb packages so we need to install the packages using apt to have tight control over this.
 #
 
-FROM debian:bullseye
+FROM debian:bookworm
 LABEL maintainer="Tim Dudgeon<[email protected]>"
 
-ENV PG_MAJOR=13
-ENV BOOST_VER=1.74.0
+ENV PG_MAJOR=15
+ENV BOOST_VER=1.81.0
 ARG DOCKER_TAG=latest
 
 RUN apt-get update &&\

Dockerfile-java-debian

@@ -1,15 +1,15 @@
 # Dockerfile for Java based RDKit implementation
 # Based on Debian.
 
-FROM debian:bullseye
+FROM debian:bookworm
 LABEL maintainer="Tim Dudgeon<[email protected]>"
 
-ARG BOOST_VER=1.74.0
+ARG BOOST_VER=1.81.0
 
 RUN apt-get update &&\
  apt-get upgrade -y &&\
  apt-get install -y --no-install-recommends\
- openjdk-11-jre-headless\
+ openjdk-17-jre-headless\
  libboost-system$BOOST_VER\
  libboost-thread$BOOST_VER\
  libboost-serialization$BOOST_VER\
@@ -28,7 +28,7 @@ COPY artifacts/debian/$DOCKER_TAG/debs/RDKit-*-Linux-Runtime.deb /tmp/
 RUN dpkg -i /tmp/*.deb && rm -f /tmp/*.deb
 WORKDIR / 
 
-ENV JAVA_HOME /usr/lib/jvm/java-11-openjdk-amd64
+ENV JAVA_HOME /usr/lib/jvm/java-17-openjdk-amd64
 ENV LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/rdkit/gmwrapper
 ENV CLASSPATH=/rdkit/gmwrapper/org.RDKit.jar
 ENV RDBASE=/usr/share/RDKit

Dockerfile-python3-debian

@@ -1,10 +1,10 @@
 # Dockerfile for Python3 based RDKit implementation
 # Based on Debian.
 
-FROM debian:bullseye
+FROM debian:bookworm
 LABEL maintainer="Tim Dudgeon<[email protected]>"
 
-ARG BOOST_VER=1.74.0
+ARG BOOST_VER=1.81.0
 
 RUN apt-get update &&\
  apt-get upgrade -y &&\ 

README.md

@@ -64,6 +64,9 @@ For each RDKit version (image tag) we build a number of images:
 * `Release_2022_09` - build from RDKit Release_2022_09 branch and occasionally rebuilt as the code gets updated. Images have tag of `Release_2022_09`
 * `Release_2022_09_4` - build from RDKit Release_2021_09_4 release tag. These images should never change [1]. Images have tag of `Release_2022_09_4`
 * `Release_2022_09_5` - build from RDKit Release_2021_09_5 release tag. These images should never change [1]. Images have tag of `Release_2022_09_5`
+* `Release_2023_03` - build from RDKit Release_2023_03 branch and occasionally rebuilt as the code gets updated. Images have tag of `Release_2023_03`
+* `Release_2023_03_1` - build from RDKit Release_2023_03_1 release tag. These images should never change [1]. Images have tag of `Release_2023_03_1`
+* `Release_2023_03_2` - build from RDKit Release_2023_03_2 release tag. These images should never change [1]. Images have tag of `Release_2023_03_2`
 
 
 [1] Where we say that the images should never change what we really mean in that the RDKit content should never change. We may rebuild these images occasionally when we find further improvements, and the underlying Centos/Debian packages may be updated, but the RDKit code should be exactly the same.