clfoundation/ecl
nightly-buster
8891731-buster
nightly-slim-buster
8891731-slim-buster
nightly-stretch
8891731-stretch
nightly-slim-stretch
8891731-slim-stretch
nightly-alpine3.13
8891731-alpine3.13
nightly-alpine3.12
8891731-alpine3.12
21.2.1-buster
buster
21.2.1-slim-buster
slim-buster
21.2.1-stretch
stretch
21.2.1-slim-stretch
slim-stretch
21.2.1-alpine3.13
alpine3.13
21.2.1-alpine3.12
alpine3.12
8891731
, nightly
nightly-buster
latest
, 21.2.1
21.2.1-buster
21.2.1-slim
, slim
21.2.1-slim-buster
nightly-slim
, 8891731-slim
nightly-slim-buster
linux/amd64
, linux/arm64
, linux/arm/v7
From ECL's Home Page:
ECL (Embeddable Common-Lisp) is an interpreter of the Common-Lisp language as described in the X3J13 Ansi specification, featuring CLOS (Common-Lisp Object System), conditions, loops, etc, plus a translator to C, which can produce standalone executables.
ECL supports the operating systems Linux, FreeBSD, NetBSD, OpenBSD, OS X, Solaris, Windows, iOS and Android, running on top of the Intel, Sparc, Alpha, PowerPC and ARM processors.
Dockerfile
in your ECL projectFROM clfoundation/ecl:latest
COPY . /usr/src/app
WORKDIR /usr/src/app
CMD [ "ecl", "--load", "./your-daemon-or-script.lisp" ]
You can then build and run the Docker image:
$ docker build -t my-ecl-app
$ docker run -it --rm --name my-running-app my-ecl-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 ECL Docker image directly:
$ docker run -it --rm --name my-running-script -v "$PWD":/usr/src/app -w /usr/src/app clfoundation/ecl:latest ecl --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 ecl-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/ecl:latest ecl --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 contains ECL binaries built from the latest source releases from the ECL devs for a variety of OSes and architectures.
This image comes in several variants, each designed for a specific use case.
clfoundation/ecl:<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. Additionally, these images contain the ECL source code (at /usr/local/src/ecl
) to help facilitate interactive development and exploration (a hallmark of Common Lisp!).
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/ecl:<version>-slim
This image does not contain the common packages contained in the default tag and only contains the minimal packages needed to run ECL. 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/ecl:<version>-alpine
This image is based on the popular Alpine Linux project, available in the alpine
official image. Alpine Linux is much smaller than most distribution base images (~5MB), and thus leads to much slimmer images in general.
This variant is highly recommended when final image size being as small as possible is desired. The main caveat to note is that it does use musl libc instead of glibc and friends, so certain software might run into issues depending on the depth of their libc requirements. However, most software doesn't have an issue with this, so this variant is usually a very safe choice. See this Hacker News comment thread for more discussion of the issues that might arise and some pro/con comparisons of using Alpine-based images.
To minimize image size, it's uncommon for additional related tools (such as git or bash) to be included in Alpine-based images. Using this image as a base, add the things you need in your own Dockerfile (see the alpine image description for examples of how to install packages if you are unfamiliar).
ECL is mostly licensed under the GNU LGPL v2+.
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/ecl