@@ -41,4 +41,30 @@ This will take a few seconds, in which the container starts, xle parses the sent
Note that the `xle` specified in the `docker run` command is the name of the tag you've given the image when building, _not_ the command to be executed (although under the hood the container will call a Linux command also called `xle`).
</details>
## :page_with_curl: About
Here, a more detailed explanation of the relevant files is given. The used sources are marked with :books:.
### `Dockerfile`
The Dockerfile specifies the steps with which the image is built. As a first step, we install dependencies:
*`xvfb`: X server, to allow XLE to display parse windows
*`imagemagick`: To take screenshots from the XLE parse windows
*`ca-certificates`: To verify the HTTPS connection to the external XLE repository
:books: [Running X applications headless using Xvfb][xvfb]
After that, we configure the external repository "Zinnwerk" which provides us with a copy of the XLE application.
:books: [Instructions to connect to a third-party repository][3rd-repo-debwiki]<br/>
:books: [How to add a third-party repo. and key in Debian?][3rd-repo-se]<br/>
:books: [apt-key Is Deprecated. How To Add OpenPGP Repository Signing Keys Without It On Debian, Ubuntu, Linux Mint, Pop!_OS, Etc.][3rd-repo-lu]
As a last step, we configure the entry point. The entry point is a script that is started inside the container whenever someone creates runs a container.
