clfoundation/ccl repository overview

⁠Supported Tags

⁠Simple Tags

• 1.12 1.12-bullseye 1.12-buster 1.12-slim 1.12-slim-bullseye 1.12-slim-buster 1.12-slim-stretch 1.12-stretch 1.12-windowsservercore 1.12-windowsservercore-1809 1.12-windowsservercore-ltsc2016 1.12-windowsservercore-ltsc2019
• 1.12.0 1.12.0-buster 1.12.0-slim 1.12.0-slim-buster 1.12.0-slim-stretch 1.12.0-stretch 1.12.0-windowsservercore 1.12.0-windowsservercore-1809 1.12.0-windowsservercore-ltsc2016
• 1.12.1 1.12.1-bullseye 1.12.1-buster 1.12.1-slim 1.12.1-slim-bullseye 1.12.1-slim-buster 1.12.1-windowsservercore 1.12.1-windowsservercore-1809 1.12.1-windowsservercore-ltsc2019
• 1.13 1.13-bookworm 1.13-bookworm-slim 1.13-trixie 1.13-trixie-slim
• 1.13.1-rc-bookworm 1.13.1-rc-bookworm-slim 1.13.1-rc-trixie 1.13.1-rc-trixie-slim
• 6c1a945 6c1a945-buster 6c1a945-slim 6c1a945-slim-buster 6c1a945-slim-stretch 6c1a945-stretch
• 27c4bc1 27c4bc1-buster 27c4bc1-slim 27c4bc1-slim-buster 27c4bc1-slim-stretch 27c4bc1-stretch
• 596fdac 596fdac-buster 596fdac-slim 596fdac-slim-buster 596fdac-slim-stretch 596fdac-stretch

⁠Shared Tags

• latest
  • 596fdac

⁠Quick Reference

CCL Home Page
https://ccl.clozure.com/⁠

Where to file Docker image related issues
https://gitlab.common-lisp.net/cl-docker-images/ccl⁠

Where to file issues for CCL itself
https://github.com/Clozure/ccl/issues⁠

Maintained by
CL Docker Images Project⁠

Supported architectures
linux/amd64, linux/arm/v7, windows/amd64

⁠What is CCL?

From CCL's Home Page⁠:

⁠How to use this image

⁠Create a Dockerfile in your CCL project

FROM 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

⁠Run a single Common Lisp script

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

⁠Developing using SLIME

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

⁠Image variants

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>-slim

This 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>-windowsservercore

This 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:

• Windows Server Quick Start⁠
• Windows 10 Quick Start⁠

⁠License

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.