- Sep 2021
-
www.opensourceflare.com www.opensourceflare.com
-
Running containers without Docker is possible with Podman.
first sighting: podman
-
-
-
Simply put: alias docker=podman.
-
What is Podman? Podman is a daemonless container engine for developing, managing, and running OCI Containers on your Linux System.
-
-
bastillebsd.org bastillebsd.org
Tags
Annotators
URL
-
- Feb 2021
-
toraritte.github.io toraritte.github.io
-
From an administrator's point of view: you can use containers. The typical solution nowadays is to create a container per service, especially when different versions are needed. That somewhat solves the problem, but at a different level and with other drawbacks. For example, needing orchestration tools, setting up a shared cache of packages, and new machines to monitor rather than simple services.
This is a very good pointer; I guess it refers to systemd services when it mentions "simple services".
-
- Jan 2021
- Nov 2020
-
github.com github.com
Tags
Annotators
URL
-
- Oct 2020
-
marketplace.visualstudio.com marketplace.visualstudio.com
- Sep 2020
-
ferd.ca ferd.ca
-
To me, abandoning all these live upgrades to have only k8s is like someone is asking me to just get rid of all error and exceptions handling and reboot the computer each time a small thing goes wrong.
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.
-
- Jul 2020
-
github.com github.com
- May 2020
-
github.com github.com
-
container technology
-
-
- Jan 2020
-
knative.dev knative.devKnative1
-
Kubernetes
Tags
Annotators
URL
-
-
feedback.azure.com feedback.azure.com
-
Azure ACI doesn't accept privileged containers. (--cap-add=NET_ADMIN)
-
- Mar 2019
-
www.thedevelopersconference.com.br www.thedevelopersconference.com.br
-
Pipeline de CI/CD no Kubernetes usando Jenkins e Spinnaker
Uau! Muitos assuntos da prova LPI DevOps são explorados nessa palestra. Fica de olho no tópico: 702 Container Management.
-
- Jan 2019
-
static1.squarespace.com static1.squarespace.com
-
as if Nature isa container.
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.
-
-
static1.squarespace.com static1.squarespace.com
-
The hero as bottle, a stringent reevaluation. I now propose the bottle as hero
Cf. Wallance Stevens, "Anecdote of the Jar"
https://www.poetryfoundation.org/poetrymagazine/poems/14575/anecdote-of-the-jar
-
- Oct 2018
-
coreos.com coreos.comCoreOS1
-
donovanhohn.blogspot.com donovanhohn.blogspot.com
Tags
Annotators
URL
-
- Sep 2018
-
www.stackrox.com www.stackrox.com
- Jul 2018
-
www.containerartistresidency01.org www.containerartistresidency01.org
-
www.containerartistresidency.org www.containerartistresidency.org
Tags
Annotators
URL
-
- Sep 2017
-
singularity.lbl.gov singularity.lbl.gov
-
Singularity containers can be used to package entire scientific workflows, software and libraries, and even data.
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.
Tags
Annotators
URL
-
- Apr 2016
-
gigadb.org gigadb.org
-
Workflow, Virtual-Machine
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/
Tags
Annotators
URL
-
- Jan 2014
-
stephane.lesimple.fr stephane.lesimple.fr
-
Difference between XZ and LZMA2 Short answer: xz is a format that (currently) only uses the lzma2 compression algorithm. Long answer: think of xz as a container for the compression data generated by the lzma2 algorithm. We also have this paradigm for video files for example: avi/mkv/mov/mp4/ogv are containers, and xvid/x264/theora are compression algorithms. The confusion is often made because currently, the xz format only supports the lzma2 algorithm (and it’ll remain the default, even if some day, others algorithms may be added). This confusion doesn’t happen with other formats/algorithms, as for example gzip is both a compression algorithm and a format. To be exact, the gzip format only supports to encapsulate data generated by gzip… the compression algorithm. In this article I’ll use “xz” to say “the lzma2 algorithm whose data is being encapsulated by the xz format”. You’ll probably agree it’s way simpler
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.
-