the Function-as-a-Service offering often have multiple fine-grained updateable code modules (functions) running within the same vm, which comes pretty close to the Erlang model.

then add service mesh, which in some cases can do automatic retry at the network layer, and you start to recoup some of the supervisor tree advantages a little more.

really fun article though, talking about the digital matter that is code & how we handle it. great reminder that there's much to explore. and some really great works we could be looking to.

Azure ACI doesn't accept privileged containers. (--cap-add=NET_ADMIN)

Uau! Muitos assuntos da prova LPI DevOps são explorados nessa palestra. Fica de olho no tópico: 702 Container Management.

Why does Kirby reject the notion of Nature as container? Is she posing containers as inert objects, 'mere' holders? Cf. Le Guin's notion of the container as another type of story.

Cf. Wallance Stevens, "Anecdote of the Jar"

https://www.poetryfoundation.org/poetrymagazine/poems/14575/anecdote-of-the-jar

Very interesting, basically Singularity allows containers to run in HPC environments, so that code running in the container can take advantage of the HPC tools, like massive scale and message passing, while at the same time keeping the stuff in the container safer.

The dockerised workflows are discussed in more detail in this blog posting here: http://blogs.biomedcentral.com/gigablog/2015/07/30/fermenting-reproducible-research-revolution/

The key here is the notion of a format as a container. Lots of content is moving towards that notion-- that a "file" is really an opaque (to the OS filesystem) directory or container of some sort and some other program understands the format of the "file" as a container to know how to open it to access the files inside.