[libre-riscv-dev] Building Docker Containers

Luke Kenneth Casson Leighton lkcl at lkcl.net
Sun Mar 29 17:24:33 BST 2020

On Sun, Mar 29, 2020 at 5:19 PM Immanuel, Yehowshua U
<yimmanuel3 at 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).


More information about the libre-riscv-dev mailing list