This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-09-17
Channels
- # announcements (17)
- # aws (2)
- # babashka (21)
- # beginners (67)
- # calva (19)
- # cider (29)
- # clara (3)
- # clj-kondo (6)
- # cljsrn (10)
- # clojure (140)
- # clojure-europe (164)
- # clojure-nl (3)
- # clojure-uk (8)
- # clojurescript (62)
- # conjure (7)
- # core-async (24)
- # cursive (21)
- # datomic (5)
- # docker (40)
- # emacs (14)
- # fulcro (25)
- # gratitude (1)
- # honeysql (6)
- # introduce-yourself (1)
- # jobs (1)
- # jobs-discuss (32)
- # juxt (7)
- # lsp (13)
- # minecraft (2)
- # off-topic (49)
- # pathom (24)
- # practicalli (8)
- # re-frame (18)
- # react (23)
- # remote-jobs (6)
- # reveal (2)
- # shadow-cljs (75)
- # tools-deps (7)
I'm moving forward with the above proposal, but only for openjdk-16+ images. openjdk-17 is a new LTS release, so that will soon become our new default for those tags that don't specify a version. This way most images will get this functionality but we won't break any existing environments using an explicit tag for openjdk-11 or lower. The PR for all that is still awaiting reviewing at https://github.com/Quantisan/docker-clojure.
@cap10morgan sounds good mostly, docker run clojure -M -e '(+ 1 2)'
looks even better though. Would it be possible to make that the default?
@mkvlr You mean make clj the ENTRYPOINT in the clojure:latest image instead of lein?
I'll open an issue about it on our GitHub repo and gather some feedback first
not currently
I could imagine some babashka variants, at least
I've been working on graalvm native-image variants lately
what does that get you?
this is using https://github.com/borkdude/deps.clj
and we start our dev env via a babashka task that uses this, so folks can run bb dev
to start it. Whatโs nice is that babashka tasks allow specifying a minimal version so this makes it easy to depend on the lastest features e.g. the recent change regarding :git/sha
instead of :sha
always a bit of a pita with the official clj
that folks get a (often crytic) error message when depending on the latest bits
hmm... so babashka could be a tool variant alongside lein, boot (does anyone use that anymore?), and tools-deps
yep, exactly ๐
s/lein/clj/ proposal: https://github.com/Quantisan/docker-clojure/issues/128
does bb clojure
need a JVM? or is it still running everything on native-image SCI?
wondering if babashka images would even need to build FROM openjdk images
well that makes things easier for me ๐
think the bb
image could just be clojure:tools-deps + https://github.com/babashka/babashka#quickstart
would you want tools.deps pre-installed? just the latest release so you wouldn't have to download it for each new container?
when I ran bb clojure
locally it still had to download a jar to ~/.deps.clj
(even though I already had that version of the cli tools installed) but maybe we could copy / symlink that ahead of time in the image
proposal issue for this: https://github.com/Quantisan/docker-clojure/issues/129
thanks!
it's a cool idea. I hadn't realized babashka could do that