permacomputing

Source repository for the main permacomputing wiki site
git clone http://git.permacomputing.net/repos/permacomputing.git # read-only access
Log | Files | Refs

commit 410489bc7fd1254d0b74e198027f20c80bb4d91c
parent e279e384d9997116ec576c4c9805aae6cdab0edd
Author: brendan <brendan@web>
Date:   Thu,  5 Mar 2026 17:18:46 +0100

create page

Diffstat:
Aeik_containers.mdwn | 8++++++++
1 file changed, 8 insertions(+), 0 deletions(-)

diff --git a/eik_containers.mdwn b/eik_containers.mdwn @@ -0,0 +1,8 @@ +Containers have some efficiency advantages but the way they are typically set up can use a lot of space on disk and eat up a lot of ram with duplicate services. Standard Debian or CentOS containers easily require 200-600MB of space. + +Docker and other popular container management systems are oriented towards more _enterprise_ scale operations where containers are frequently set up and torn down with automated cloud orchestration tools. + +If we want to have a more PMC take on containers, what we need probably looks more like a few tiny linux matryoshka dolls. Alpine Linux is based on musl (instead of libc), Busybox (instead of GNU-derived toolchain) and OpenRC (instead of systemD) and gives us a bare-bones but very utilitarian base container image in just 16MB. We can, with a little bit of manual effort get this to run in a systemd-nspawn container. + +### Build a new alpine container +