From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: Libre-RISCV General Development <libre-riscv-dev@lists.libre-riscv.org>
Subject: Re: [libre-riscv-dev] Building Docker Containers
Date: Sun, 29 Mar 2020 16:24:33 +0000
Message-ID: <CAPweEDx+Cg-wota_Np-LyyvSxkT=Kt-YJwhe=oB719=Gf88vuQ@mail.gmail.com> (raw)
In-Reply-To: <4B863442-6244-4412-92B0-EA073D1A6CEB@gatech.edu>
On Sun, Mar 29, 2020 at 5:19 PM Immanuel, Yehowshua U
<yimmanuel3@gatech.edu> wrote:
> > snapshots. the key word there is: snapshots. as in, "something that
> > is expected to be thrown away rather than upgraded". as in, a
> > *multi-gigabyte download*.... each time.
>
> Docker DOES pull in commit layers. So you can specify layers. Like a GIt layer onto of a python layer, ontop of a ubuntu layer etc. So docker can check which layers changed and just update those - so no need for huge downloads everytime IF you specify docker layer dependencies correctly.
>
> You usually do this in your docker file with “from ubuntu:” for “from python3”
> You can also build your own layers etc…
yes. not interested [and don't have time to find out what the hell is
going on]. not after the complete failure of exactly such a "layer"
setup involving google auth, kubernetes and couchdb 2.3.1 *stable*
docker release resulted in a 1.2 GB download.
i don't trust it, have never liked it, it's badly written, insecure,
and just because everyone in the world thinks it's the best thing ever
doesn't actually make that true - not to someone who's done pretty
much every major type of virtual container for linux that's existed
since 1995. (i manage a 15-year-old server that went through *three*
live conversions: XEN, to KVM, to LXC where it is, now).
l.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
next prev parent reply index
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-29 13:48 Immanuel, Yehowshua U
2020-03-29 15:26 ` Luke Kenneth Casson Leighton
2020-03-29 16:03 ` Immanuel, Yehowshua U
2020-03-29 16:14 ` Luke Kenneth Casson Leighton
2020-03-29 16:19 ` Immanuel, Yehowshua U
2020-03-29 16:24 ` Luke Kenneth Casson Leighton [this message]
2020-03-29 17:21 ` Jacob Lifshay
2020-03-29 18:48 ` Luke Kenneth Casson Leighton
2020-03-29 18:59 ` Jacob Lifshay
2020-03-29 19:33 ` Immanuel, Yehowshua U
2020-03-29 19:56 ` Jacob Lifshay
2020-03-29 19:57 ` Luke Kenneth Casson Leighton
2020-03-29 20:02 ` Jacob Lifshay
2020-03-29 20:51 ` Cole Poirier
2020-03-29 21:12 ` Luke Kenneth Casson Leighton
2020-03-29 21:34 ` Cole Poirier
2020-03-30 8:59 ` Luke Kenneth Casson Leighton
2020-03-30 18:13 ` Jacob Lifshay
2020-03-30 18:43 ` Cole Poirier
2020-03-30 18:58 ` Luke Kenneth Casson Leighton
2020-03-30 19:08 ` Jacob Lifshay
2020-03-30 19:31 ` Cole Poirier
2020-03-29 16:19 ` Luke Kenneth Casson Leighton
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='CAPweEDx+Cg-wota_Np-LyyvSxkT=Kt-YJwhe=oB719=Gf88vuQ@mail.gmail.com' \
--to=lkcl@lkcl.net \
--cc=libre-riscv-dev@lists.libre-riscv.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
Libre RISC-V Mailing list Archives (accessible via public-inbox)
Archives are clonable: git clone --mirror https://inbox.libre-soc.org/libre-riscv-dev
Example config snippet for mirrors
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git