texlive

中文版

Customized TeX Live Docker image for VSCode LaTeX Workshop.

DockerHub Image

Why This Image?

This Docker image ensures that you can compile LaTeX documents locally even when you cannot connect to Overleaf. It provides a consistent and reproducible environment for LaTeX compilation, including all necessary packages and tools.

Features

How to Use with VSCode LaTeX Workshop

Prerequisites

  1. Install Docker.
  2. Install the LaTeX Workshop extension in VSCode.

Configuration

Add the following settings to your settings.json in VSCode to use the Docker image for LaTeX compilation:

"latex-workshop.docker.enabled": true,
"latex-workshop.docker.image.latex": "oaklight/texlive:latest-science",
"latex-workshop.latex.clean.subfolder.enabled": true,
"latex-workshop.latex.recipes": [
  {
    "name": "latexmk",
    "tools": [
      "latexmk"
    ]
  }
],
"latex-workshop.latex.tools": [
  {
    "name": "latexmk",
    "command": "latexmk",
    "args": [
      "-synctex=1",
      "-interaction=nonstopmode",
      "-file-line-error",
      "-lualatex",
      "-outdir=%OUTDIR%",
      "%DOC%"
    ],
    "env": {}
  }
],
"latex-workshop.latex.autoBuild.run": "onSave",
"latex-workshop.latex.clean.method": "glob"

Steps

  1. Pull the Docker image:
   docker pull oaklight/texlive:latest-science
  1. Open your LaTeX project in VSCode.
  2. Save your settings.json with the above configuration.
  3. Open a .tex file and start editing. The LaTeX Workshop extension will automatically use the Docker image for compilation.

Building the Image Locally

If you want to build the Docker image locally, use the provided Makefile :

  1. Clone this repository.
  2. Run:
   make build

This will build the image with the tags oaklight/texlive:latest and oaklight/texlive:latest-science .

Pushing the Image (Optional)

If you want to push the image to a Docker registry:

make push

Cleaning Up

To remove the Docker image:

make clean

Supported LaTeX Features

Troubleshooting

License

This project is licensed under the MIT License. See the LICENSE file for details.