Hi Thangalin, Some thoughts on your comments below:
> On 25 Nov 2025, at 19:48, Thangalin <[email protected]> wrote: > > Just as a reminder, there are already instructions for installing ConTeXt > into a Docker container on the Wiki. No need to hack the Keenwrite version. > > <https://wiki.contextgarden.net/Installing_ConTeXt_LMTX_into_a_Docker_container> > > Some possible issues with the container code on that page: > > * Inkscape isn't installed, so SVG files may not fully work in all cases. Fair point, I can see if I can add that. > * The base image (debian:latest) has a far larger footprint than needed > (alpine:latest is minimal). I think, at the time, there was no MUSL version of ConTeXt so Alpine couldn't be used. It can be swapped but unless someone is planning to run a vast swarm of ConTeXt containers the image size isn't really an issue. (And if they are they'll already know how to reduce it.) > * Lots of files remain that are not needed, bloating the image more than > necessary (e.g., PDF docs). Not sure what you mean here. The ConTeXt PDF documentation is retained because it's part of the distribution. > * No extra fonts are installed, so users may have to modify the container > anyway to add those fonts. There's no way to know what fonts people might want, so maybe some commented-out lines could be included as an example to show people how to add a font but it wouldn't get added by default. > * Certificates may not be up to date. ConTeXt doesn't use any certificates, afaik. If the installer uses tools such as 'curl' and they use certificates then the base OS container takes care of it. > * May be helpful to set OSFONTDIR. I didn't need it when I was testing the container but might be needed if additional fonts are added. > * Relies on Docker (and Docker names), which isn't free on all platforms; > podman is free on all systems. I'm not sure what the issue is here. The page uses standard Docker terminology so that it will build on a Docker installation. If someone wishes to use podman or Orbstack or one of the several other container build/runtime environments available instead then they are expected to consult the documentation that comes with their preferred system to understand what changes need to be made. Sticking to standard terminology makes that simpler. (Or, put another way, if you replaced the wiki page with a podman version using container files and 'podman' on the command line then there would soon be a plea on the mailing list "Is there a docker version?") As for cost: the command line version of Docker is still free and is fine for running a single instance; and some users may well be companies who choose to pay for Docker so they can obtain support - it's not our place to make that choice for them. > * Nit: Hard-coded references to "linux-64" could use a variable, instead. The container base OS is linux-64 so it just got hard-coded. If an Alpine version is created then it might make sense to move it to a variable then. Regards, — Bruce Horrocks Hampshire, UK ___________________________________________________________________________________ If your question is of interest to others as well, please add an entry to the Wiki! maillist : [email protected] / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror) archive : https://github.com/contextgarden/context wiki : https://wiki.contextgarden.net ___________________________________________________________________________________
