> > I'm not sure what the issue is here. > It's a pet peeve of mine: using a specific term instead of a general term when writing software and configuration files.
Instead of a "Docker" image you can make a container image that works with both Docker and podman. Instead of a "Dockerfile" you can call it a "Containerfile" and it'll work with both podman and Docker and whatever other containerization platform comes out in the future. For documentation you can write, "works with Docker and podman" to help the searchers. Speaking of images, another issue with the wiki's example is that there isn't an obvious way to import external images from outside the container environment (i.e., no external directory paths are mapped). Anyway, I recommend looking at the Containerfile I put together, as it adds a number of features to running containerized ConTeXt. Feel free to pilfer or not. Cheers!
___________________________________________________________________________________ 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 ___________________________________________________________________________________
