Fork me on GitHub
#circleci
<
2022-11-24
>
lread18:11:58

Currently looking at cimg/clojure and I'm thinking that maybe CircleCI doesn't update their new convenience images as much as they did their legacy versions back in the day.

❯ docker run -i -t cimg/clojure:1.11.1     
circleci@3bb12fd2ab39:~/project$ clojure --version
Clojure CLI version 1.11.1.1105
circleci@3bb12fd2ab39:~/project$ java --version
openjdk 17.0.2 2022-01-18
OpenJDK Runtime Environment Temurin-17.0.2+8 (build 17.0.2+8)
OpenJDK 64-Bit Server VM Temurin-17.0.2+8 (build 17.0.2+8, mixed mode, sharing)
I mean sure, we can always install newer versions in config steps, but maybe that defeats the purpose of a custom clojure image a bit?

lread18:11:16

Maybe the clojure https://github.com/Quantisan/docker-clojure/blob/master/README.md are a better choice these days.

❯ docker run -i -t --entrypoint /bin/bash clojure:latest                       
root@81ac3017d6ae:/tmp# clojure --version
Clojure CLI version 1.11.1.1200
root@81ac3017d6ae:/tmp# java --version
openjdk 17.0.5 2022-10-18
OpenJDK Runtime Environment Temurin-17.0.5+8 (build 17.0.5+8)
OpenJDK 64-Bit Server VM Temurin-17.0.5+8 (build 17.0.5+8, mixed mode, sharing)

glenjamin20:11:40

Since docker images are just tarballs from S3, my advice would be to use the Java image and add any extra clojure stuff needed via a step which pulls stuff off S3 If you pull something uncompressed from us-east-1 it’ll actually be faster than a docker layer