@@ -47,14 +54,96 @@ From [ABCL's Home Page](https://abcl.org)
> Armed Bear Common Lisp (ABCL) is a full implementation of the Common Lisp language featuring both an interpreter and a compiler, running in the JVM. Originally started to be a scripting language for the J editor, it now supports JSR-223 (Java scripting API): it can be a scripting engine in any Java application. Additionally, it can be used to implement (parts of) the application using Java to Lisp integration APIs.
<aid="org5fd92f5"></a>
<aid="org0c93268"></a>
# What's in the image?
# How to use this iamge
This image contains ABCL binaries released by the upstream devs.
$docker run -it--rm--name my-running-app my-abcl-app
```
<aid="orge3a1ae4"></a>
## 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 ABCL Docker image directly:
[SLIME](https://common-lisp.net/project/slime/) provides a convenient and fun environment for hacking on Common Lisp. To develop using SLIME, first start the Swank server in a container:
```console
$docker run -it--rm--name abcl-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/abcl:latest abcl --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:
```emacs
M-x slime-connect RET RET RET
```
<aid="org6244e31"></a>
# Image variants
This image comes in several variant, each designed for a specific use case.
<aid="org87740a4"></a>
## `clfoundation/abcl:<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.
This tag attempts to replicate the base environment provided by buildpack-deps. It, by design, has a large number of extremely common Debian packages.
<aid="org5224a51"></a>
## `clfoundation/abcl:<version>-slim`
This image does not contain the common packages contained in the default tag and only contains the minimal packages needed to run ABCL. 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.
This image is based on [Windows Server Core (`microsoft/windowsservercore`)](https://hub.docker.com/_/microsoft-windows-servercore). 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](https://msdn.microsoft.com/en-us/virtualization/windowscontainers/quick_start/quick_start_windows_server)