custom enriched Japanese TeX Live environment image
3.3K
custom enriched Japanese TeX Live environment image
Dockerfile linkslatest = 2026 = 2026.20260314: TeX Live 2026 current (x86_64-linux, aarch64-linux)2025 = 2025.20260628, 2025-custom = 2025-custom.20260628: TeX Live 2025 frozen (x86_64-linux, aarch64-linux)2024 = 2024.20260628, 2024-custom = 2024-custom.20260628: TeX Live 2024 frozen (x86_64-linux, aarch64-linux)2023 = 2023.20260628, 2023-custom = 2023-custom.20260628: TeX Live 2023 frozen (x86_64-linux, aarch64-linux)2022 = 2022.20240225: TeX Live 2022 frozen (x86_64-linux, aarch64-linux)2021 = 2021.20221111: TeX Live 2021 frozen (x86_64-linux, aarch64-linux)2020 = 2020.20220907: TeX Live 2020 frozen (x86_64-linux, aarch64-linux)2019 = 2019.20221112: TeX Live 2019 frozen (x86_64-linux, aarch64-linux)2018 = 2018.20220614: TeX Live 2018 frozen (x86_64-linux, aarch64-linux)2017 = 2017.20230508: TeX Live 2017 frozen (x86_64-linux, aarch64-linux)2016 = 2016.20240303: TeX Live 2016 frozen (x86_64-linux)2015 = 2015.20240303: TeX Live 2015 frozen (x86_64-linux)2014 = 2014.20240303: TeX Live 2014 frozen (x86_64-linux)2013 = 2013.20240303: TeX Live 2013 frozen (x86_64-linux)2012 = 2012.20240303: TeX Live 2012 frozen (x86_64-linux)These images contain the following components:
Some tags below have additional/reduced packages:
20260114 or higher
20250430 or higher
20240708 or higher
20240323 or higher
20240225 or higher
20230602 or higher
20230506 or higher
20220614 or higher
Each <year>-custom tag replaces the xdvipdfmx binary in the corresponding <year> tag with one built from svn r78557 (svn://tug.org/texlive/trunk/Build/source@78557) by GitHub Actions via github.com/TeX-Live/texlive-source.
In due course, this CI-built xdvipdfmx binary will be replaced again with an officially built one — either when an official xdvipdfmx binary becomes available before TeX Live 2026 is frozen, or as soon as TeX Live 2027 is released, whichever comes first.
We also have pushed the latest image to the GitHub Container Registry.
munepi/tllangjapanese containerA common use of the image looks like this (linebreaks for readability):
docker run --rm \
--volume "$(pwd):/data" \
--user $(id -u):$(id -g) \
munepi/tllangjapanese:latest lualatex foo.tex
This will convert the LaTeX document file foo.tex in the current working directory into the PDF output file foo.pdf.
Note that Docker options go before the image name, here munepi/tllangjapanese, while lualatex options come after it.
The --volume flag maps some local directory (lefthand side of the colons) to a directory in the container (righthand side), so that you have your source files available for lualatex to convert.
$(pwd) is quoted to protect against spaces in filenames.
Ownership of the output file is determined by the user executing lualatex in the container.
This will generally be a user different from the local user.
It is hence a good idea to specify for docker the user and group IDs to use via the --user flag.
munepi/tllangjapanese is based on a custom Debian GNU/Linux image with the following packages:
munepi/pandoc https://hub.docker.com/r/munepi/pandocmunepi/review https://hub.docker.com/r/munepi/reviewMunehiro Yamamoto https://github.com/munepi
Content type
Image
Digest
sha256:f609c084c…
Size
810.7 MB
Last updated
23 days ago
docker pull munepi/tllangjapanese:2024.20260628