pandoc/latex:latest-ubuntu - tlmgr: Local TeX Live (2024) is older than remote repository (2025).

[falk-w]

When running:

docker -- run --rm --platform linux/amd64 --volume $(pwd):/data \
    --entrypoint /bin/bash \
    pandoc/latex:latest-ubuntu \
    -c "set -xe; \
    # Update tlmgr and install the necessary packages and fonts
    apt-get update && apt-get install -y fonts-open-sans fonts-freefont-ttf; \
    # Show current TeX Live version
    tlmgr version; \
    # We need to update TeX Live to get the latest packages
    tlmgr update --self && \
    tlmgr version; \
    # Install the necessary packages
    tlmgr install extsizes pdflscape titlesec; \
    # Create PDF with pandoc
    /usr/local/bin/pandoc --pdf-engine=xelatex \
    --listings -H listings-setup.tex \
    --metadata-file=$TITLE_FILE \
    --metadata-file=parameters.yaml \
    -H $FOOTER_FILE \
    \
    -s \
    whitepaper.md \
    \
    -o whitepaper.pdf"

It fails with: Local TeX Live (2024) is older than remote repository (2025)

Details:

+ tlmgr version
tlmgr revision 73493 (2025-01-17 23:28:29 +0100)
tlmgr using installation: /opt/texlive/texdir
TeX Live (https://tug.org/texlive) version 2024
+ tlmgr update --self

tlmgr: Local TeX Live (2024) is older than remote repository (2025).
Cross release updates are only supported with
  update-tlmgr-latest(.sh/.exe) --update
See https://tug.org/texlive/upgrade.html for details.
+ tlmgr install extsizes pdflscape titlesec

tlmgr: Local TeX Live (2024) is older than remote repository (2025).
Cross release updates are only supported with
  update-tlmgr-latest(.sh/.exe) --update
See https://tug.org/texlive/upgrade.html for details.

[rv0lt]

It seems that they need to re-build the docker image https://github.com/pandoc/dockerfiles/blob/main/release-checklist.md#case-texlive-was-frozen

[falk-w]

I assume it will be addressed with: #265

[falk-w]

Workaround available here: #265 (comment)

[rv0lt]

Going to the closed issues, it seems that it is a yearly problem that happens every year around April.
In our case we use it for a GitHub Action so we need to wait it for a new release on their part