Wrapping Clojure Tooling in Containers
summary
Argues that packaging Clojure tooling into containers yields a repeatable, sharable dev image and demos the pieces: builds a Dockerfile with Java JDK and Leiningen, runs a container that upgrades host Java 1.7 to Java 1.8 inside, mounts host .m2 to avoid redownloading, uses make targets and docker exec to spawn shells, creates a matching UID/GID startup script to avoid root-owned files, starts a Ring server from the container, runs Emacs GUI via exer and exposes the container JDK to IntelliJ via sshfs with follow-symlinks; demos mostly work despite small glitches.
AI-written summary · about
chapters (4)
related talks
40mJdeps, Jlink and Layers: Slim Down Your Java Docker Images
46mDockerfiles, Buildpacks, Jib and more, best way to run Java code in Containers?
31mFast and Distroless Java in Containers: the Recipe!
46mWrite Once, Run Anywhere? Building Perfect Docker Images for Java Apps
41mContinuous Delivery with Docker Containers and Java EE
32mDistroless Docker: Containerizing Apps, not VMs
47mMission Possible: The 45-Minute Path to Bullet-Proof Java Container Images
55mTransforming Enterprise Development With Clojure