From: Albert Krewinkel <albert+pandoc-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: ANN: new Docker image tagging scheme
Date: Thu, 13 Jan 2022 11:04:06 +0100 [thread overview]
Message-ID: <87k0f4vsfs.fsf@zeitkraut.de> (raw)
I'm pleased to announce the release of new pandoc Docker images for
pandoc 2.17, as well as a new image tagging scheme:
- The list of supported image tags is now explicitly listed in the
Docker Hub repository readme. For logistical reasons, we will
support not more that around six or seven released versions.
- Version tags are now "rolling", meaning that numerical versions will
always point to the latest release that has the given version
prefix. E.g., the tag `2.16` points to `2.16.2.0`. This is a common
convention for Docker images. Use a four-part version tag to point
to a specific release, e.g. `2.17.0.0`.
- The `pandoc-crossref` filter is now available in `pandoc/core`
images, as is a image library used to convert SVG images. Use the
new `pandoc/minimal` repository for truly minimal imges.
- A new stack "static" was introduced for `pandoc/minimal` images. The
images contain just a statically compiled pandoc binary, but no OS.
This is especially helpful when including pandoc into other Docker
containers, e.g.
COPY --from=pandoc/minimal:latest /pandoc /usr/bin/pandoc
- The OS of an image can be controlled by appending the identifier to
the version tag. E.g., to get the newest release in a pandoc+LaTeX
image, use `pandoc/latex:latest-ubuntu`.
- The repositories `pandoc/alpine`, `pandoc/ubuntu`,
`pandoc/alpine-crossref`, `pandoc/ubuntu-crossref`,
`pandoc/alpine-latex`, and `pandoc/ubuntu-latex` are deprecated and
will no longer receive updates or new versions. Please use one of
the three supported repositories with a respective tag.
Please refer to the image repositories for additional info:
- minimal: <https://hub.docker.com/r/pandoc/minimal>
- core: <https://hub.docker.com/r/pandoc/core>
- latex: <https://hub.docker.com/r/pandoc/latex>
Many thanks to Stephen McDowell and Caleb Maclennan for their continued
help and support; maintaining Docker images would not be possible
without their help!
--
Albert Krewinkel
GPG: 8eed e3e2 e8c5 6f18 81fe e836 388d c0b2 1f63 1124
next reply other threads:[~2022-01-13 10:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-13 10:04 Albert Krewinkel [this message]
[not found] ` <87k0f4vsfs.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2022-01-13 14:05 ` Albert Krewinkel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k0f4vsfs.fsf@zeitkraut.de \
--to=albert+pandoc-9eawchwdxg8hfhg+jk9f0w@public.gmane.org \
--cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).