A docker container for building LaTeX documents. Designed for DSczyrba/Vorlage-Latex
The container is supposed to be created and run exactly once per build.
docker run --rm -v "$(pwd):/latex" ghcr.io/jemand771/latex-build
This will try to build the file main.tex in the current working directory into a main.pdf. See below for more info on configuration options.
It's recommended to not have the container run as root internally but rather with the same uid:gid as the user on the host system. This can be achieved by specifying
docker run -u $(id -u ${USER}):$(id -g ${USER}) [...]
Some features like diff-pdf might require the container to be run with an it process like this:
docker run --init [...]
There will notes on all affected features in the feature list below.
Environment variables for the container can be set using the -e flag. Use the flag multiple times if you'd like to set multiple parameters.
docker run -e FOO=BAR -e HELLO=WORLD [...]
The table below lists all environment variables declared in the Dockerfile. You may modify all of them in any way you like, however, certain values might cause unexpected behaviour. Stick to the instructions in the features chapter if you're unsure.
| variable name | default value | description |
|---|---|---|
| BIND_PATH | /latex | The path specified after -v the container will use internally. There is no need to change this unless you're integrating this container into a build script that can't be changed. |
| BUILD_DIRECTORY | .build | The name of the temporary directory used for building. This will appear inside both $BIND_PATH and the host folder bound to it. Change this if you don't like the name. |
| CLEAN_BUILD | Set this to a non-empty value to enable clean builds - this will delete the $BUILD_DIRECTORY folder bevore proceeding. |
|
| DELETE_TEMP | Like clean builds, but the other way around: Build and clean up afterwards (note: this might still use the build cache from before if it exists.) | |
| DISABLE_DIFFPDF | Set to non-empty value to disable the diff-pdf feature. See below. | |
| DISABLE_PYTHONTEX | Set to non-empty value to disable the pythontex feature. See below. | |
| DISABLE_SYNCTEX | Set to non-empty value to disable the synctex feature. See below. | |
| HOST_PATH | Optional argument to tell the container which path $BIND_PATH is bound to. Set this to the host path specified after -v. |
|
| TARGET | main | Name of the LaTeX target file without extension. All resulting files will be named after this, i.e. $TARGET.pdf, $TARGET.synctex.gz, ... |
| WARNINGS | -Wall | Warning options to pass to latexrun.py. Use this to silence certain warnings. |
By default, all optional container features are enabled. See above on how to disable features you don't need.
This container uses latexrun to build LaTeX documents which itself uses pdflatex and biber. It (latexrun) dertermines whether pdflatex needs to run again in order to keep compilation times low.
When launching the container, all files in the bound path will be copied to a temporary subfolder (called .build by default, name is configurable) and compilation will run there. After that, all important output files (namely the output PDF) will be copied back to where the source files came from. This has the advantage of not cluttering your working directory while still telling pdflatex to use . as the target folder (a cd is done inside the container). Otherwise, some packages (e.g. minted) may not work properly because they can't find their cache.
This container may use diff-pdf to generate a second PDF file highlighting the differences between the previous and current build. Note that this takes a couple of seconds, so if you don't need this, you should probably disable it.
Important note: this feature requires the docker container to be launched with the --init flag.
This container can handle documents containing PythonTeX. This means that python code can be executed at LaTeX compile time. To achieve support for this, pdflatex and pythontex need to be run before compiling the actual document. This feature doesn't add much compile time if you leave it enabled without using it.
This container can generate a synctex.gz file for you. Because all of the paths inside that file will refer to the folder structure inside the container (/latex/.build/<bla>), we rewrite this file by replacing all known-bound paths with their corresponding host paths. This way, forward and reverse synctex works for all of the local project files. (however, it doesn't work for installed packages since their location might be completely different)
In order to use this feature, you need to set the environment variable HOST_PATH to the same folder you bound /latex to. (the part before the colon). If you don't set this variable, a synctex file will still be generated but it won't be usable by your editor (wrong contents/paths. You can use the option specified above disable synctex generation completely.
This repo supports registering additional pygments lexers (the "renderers" for the LaTeX package minted) at build time. These can be refered to by any one of their aliases listed below. (e.g. \begin{minted}{custom-regex})
| name | description | aliases |
|---|---|---|
custom-regex |
A lexer for highlighting regular expressions. (ps: don't confuse this with the RegexLexer base class for all pygments lexers.) |
custom-regex |
If you have any questions, feature requests or LaTeX package suggestions, feel free to open an issue here on GitHub.