From: Leah Neukirchen via ntg-context <ntg-context@ntg.nl>
To: <ntg-context@ntg.nl>
Cc: Leah Neukirchen <leah@vuxu.org>
Subject: Re: Containerized ConTeXt
Date: Wed, 14 Dec 2022 14:15:56 +0100 [thread overview]
Message-ID: <87wn6up1mb.fsf@vuxu.org> (raw)
In-Reply-To: <CAANrE7o0OF9O6-aHoM2vQYSfd8PPMYcpkUGJ2Di2fzCpVj_abQ@mail.gmail.com> (Thangalin via ntg-context's message of "Tue, 13 Dec 2022 20:56:28 -0800")
Thangalin via ntg-context <ntg-context@ntg.nl> writes:
> Thoughts? Suggestions for improvement?
If you are looking for technical suggestions, every RUN line will
create a layer even if you delete files later. I'd suggest making the
final image by copying the root directory of a multistage container,
e.g. https://adriancitu.com/2022/03/11/7-ways-to-build-lighter-linux-containers/
Alternatively, do all the steps before installing ConTeXt in a
multistage container, and run all shell commands that install ConTeXt
in one action, then you get two layers and the lower one only changes
if a font changes (or alpine:latest).
--
Leah Neukirchen <leah@vuxu.org> https://leahneukirchen.org/
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2022-12-14 13:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-14 4:56 Thangalin via ntg-context
2022-12-14 13:15 ` Leah Neukirchen via ntg-context [this message]
2022-12-14 13:40 ` Henri Menke via ntg-context
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=87wn6up1mb.fsf@vuxu.org \
--to=ntg-context@ntg.nl \
--cc=leah@vuxu.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).