pandoc/dockerfiles

pandoc/latex:latest ships broken tlmgr ("tlmgr itself needs to be updated")

jendrikw opened this issue · 1 comments

podman pull pandoc/latex:latest

Trying to pull docker.io/pandoc/latex:latest...
Getting image source signatures
Copying blob 97518928ae5f skipped: already exists  
Copying blob 2778b116be1e done  
Copying blob 857bc227a873 done  
Copying blob 91616de770f8 done  
Copying blob 88aac0ab9e9a done  
Copying blob d1ab3b298b51 done  
Copying blob d47f37edb4a1 done  
Copying blob f16ae19e24e0 done  
Copying blob d3f51472a425 done  
Copying blob caaae16c01dc done  
Copying blob 6e0dad58dd3a done  
Copying config bdc3db975c done  
Writing manifest to image destination
Storing signatures
bdc3db975cdc275c70ca1706a66c00a68dd348d3ee97ecda4c4ff94acadd2351

podman run --rm -ti --entrypoint sh pandoc/latex:latest -c 'tlmgr install fvextra'

tlmgr: package repository https://mirror.mwt.me/ctan/systems/texlive/tlnet (verified)
===============================================================================
tlmgr itself needs to be updated.
Please do this via either
  tlmgr update --self
or by getting the latest updater for Unix-ish systems:
  https://mirror.ctan.org/systems/texlive/tlnet/update-tlmgr-latest.sh
and/or Windows systems:
  https://mirror.ctan.org/systems/texlive/tlnet/update-tlmgr-latest.exe
Then continue with other updates as usual.
===============================================================================
tlmgr: Terminating; please see warning above!

Thanks for the report. This happens frequently and matters for users who build their own images based. However, running the suggested tlmgr update --self when building a derived image should be enough to fix this.

It would certainly be nice if this wasn't necessary. However, given that the fix is simple, and rebuilding the images each time tlmgr is updated does not seem worth the effort, we asks users to accept this inconvenience and to work around it as described.

If you think this could be documented better, please let us know. PRs with the suggested documentation changes are especially welcome.