New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update Docker Hub image (2.9.6980 -> 2.9.7050) #13
Comments
Yes, a fresh official rebuild would be nice. Latest tag
|
I built an unofficial one, which might help: https://hub.docker.com/r/nanmu42/miktex-docker . |
@nanmu42 Have you tested your unofficial version? Because your version gives the same error, but with different versions:
|
Could you provide a minimal example to reproduce this error? |
After performing a clean reinstall, cleaning all auxiliary files, and some debugging, I managed to get both Docker images to work. Because TeX packages are constantly changing and MiKTeX downloads them on demand, one always has to update MiKTeX repositories before using any image. The solution is to use the official Docker image $ sudo docker run -it -v $(pwd):/miktex/work miktex/miktex bash
$ mpm --admin --update
$ latexmk example.tex Consider adding If anyone is interested in a trivial example that uses XeLaTeX and Biber to compile to PDF:
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Bumping for visibility: An update of the official build on dockerhub is very appreciated |
Yep, the docker hub image is outdated since August! |
Hello there! Could you please release a fresh image to the Docker Hub?
I tried to use the docker hub image to build my document using:
docker run --rm -ti -v C:\some\path:/miktex/work miktex/miktex pdflatex root.tex
But it failed while downloading some packages:
I think that this is the problem because building the document just worked fine when I built the docker image on my own.
Building the docker image on my own resulted in MiKTeX
v2.9.7050
living inside the container instead ofv2.9.6980
.Have a nice day! 😃
The text was updated successfully, but these errors were encountered: