nightly-buster596fdac-busternightly-slim-buster596fdac-slim-busternightly-stretch596fdac-stretchnightly-slim-stretch596fdac-slim-stretch1.12-busterbuster1-buster1.12.0-buster1.12-slim-busterslim-buster1-slim-buster1.12.0-slim-buster1.12-stretchstretch1-stretch1.12.0-stretch1.12-slim-stretchslim-stretch1-slim-stretch1.12.0-slim-stretch1.12-windowsservercore-1809windowsservercore-18091-windowsservercore-18091.12.0-windowsservercore-18091.12-windowsservercore-ltsc2016windowsservercore-ltsc20161-windowsservercore-ltsc20161.12.0-windowsservercore-ltsc2016596fdac-slim, nightly-slimnightly-slim-buster1-slim, 1.12.0-slim, slim, 1.12-slim1.12-slim-busterlatest, 1, 1.12, 1.12.01.12-buster1.12-windowsservercore-18091.12-windowsservercore-ltsc2016windowsservercore, 1-windowsservercore, 1.12.0-windowsservercore, 1.12-windowsservercore1.12-windowsservercore-18091.12-windowsservercore-ltsc2016nightly, 596fdacnightly-busterlinux/amd64, linux/arm/v7, windows/amd64From CCL's Home Page:
Clozure CL (often called CCL for short) is a free Common Lisp implementation with a long history. Some distinguishing features of the implementation include fast compilation speed, native threads, a precise, generational, compacting garbage collector, and a convenient foreign-function interface.
Dockerfile in your CCL projectFROM clfoundation/ccl:latest
COPY . /usr/src/app
WORKDIR /usr/src/app
CMD [ "ccl", "--load", "./your-daemon-or-script.lisp" ]
You can then build and run the Docker image:
$ docker build -t my-ccl-app
$ docker run -it --rm --name my-running-app my-ccl-app
For many simple, single file projects, you may find it inconvenient to write a complete `Dockerfile`. In such cases, you can run a Lisp script by using the CCL Docker image directly:
$ docker run -it --rm --name my-running-script -v "$PWD":/usr/src/app -w /usr/src/app clfoundation/ccl:latest ccl --load ./your-daemon-or-script.lisp
SLIME provides a convenient and fun environment for hacking on Common Lisp. To develop using SLIME, first start the Swank server in a container:
$ docker run -it --rm --name ccl-slime -p 127.0.0.1:4005:4005 -v /path/to/slime:/usr/src/slime -v "$PWD":/usr/src/app -w /usr/src/app clfoundation/ccl:latest ccl --load /usr/src/slime/swank-loader.lisp --eval '(swank-loader:init)' --eval '(swank:create-server :dont-close t :interface "0.0.0.0")'
Then, in an Emacs instance with slime loaded, type:
M-x slime-connect RET RET RET
This image comes in several variants, each designed for a specific use case.
clfoundation/ccl:<version>This is the defacto image. If you are unsure about what your needs are, you probably want to use this one. It is designed to be used both as a throw away container (mount your source code and start the container to start your app), as well as the base to build other images off of.
Some of these tags may have names like buster or stretch in them. These are the suite code names for releases of Debian and indicate which release the image is based on. If your image needs to install any additional packages beyond what comes with the image, you'll likely want to specify one of these explicitly to minimize breakage when there are new releases of Debian.
These images are built off the buildpack-deps image. It, by design, has a large number of extremely common Debian packages.
These images contain the Quicklisp installer, located at /usr/local/share/common-lisp/source/quicklisp/quicklisp.lisp. Additionally, there is a script at /usr/local/bin/install-quicklisp that will use the bundled installer to install Quicklisp. You can configure the Quicklisp install with the following environment variables:
QUICKLISP_DIST_VERSION: The dist version to use. Of the form yyyy-mm-dd. latest means to install the latest version (the default).QUICKLISP_CLIENT_VERSION: The client version to use. Of the form yyyy-mm-dd. latest means to install the latest version (the default).QUICKLISP_ADD_TO_INIT_FILE: If set to true, (ql:add-to-init-file) is used to add code to the implementation's user init file to load Quicklisp on startup. Not set by default.Additionally, these images contain cl-launch to provide a uniform interface to running a Lisp implementation without caring exactly which implementation is being used (for instance to have uniform CI scripts).
clfoundation/ccl:<version>-slimThis image does not contain the common packages contained in the default tag and only contains the minimal packages needed to run CCL. Unless you are working in an environment where only this image will be deployed and you have space constraints, we highly recommend using the default image of this repository.
clfoundation/ccl:<version>-windowsservercoreThis image is based on Windows Server Core (microsoft/windowsservercore). As such, it only works in places which that image does, such as Windows 10 Professional/Enterprise (Anniversary Edition) or Windows Server 2016.
For information about how to get Docker running on Windows, please see the relevant "Quick Start" guide provided by Microsoft:
CCL is licensed under the Apache v2.0.
The Dockerfiles used to build the images are licensed under BSD-2-Clause.
As with all Docker images, these likely also contain other software which may be under other licenses (such as Bash, etc from the base distribution, along with any direct or indirect dependencies of the primary software being contained).
As for any pre-built image usage, it is the image user's responsibility to ensure that any use of this image complies with any relevant licenses for all software contained within.
docker pull clfoundation/ccl