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 8886a7543d066c1a9ea5caa48d5ccb745d011970
parent 410489bc7fd1254d0b74e198027f20c80bb4d91c
Author: brendan <brendan@web>
Date:   Mon,  9 Mar 2026 09:54:55 +0100


Diffstat:
Meik_containers.mdwn | 23++++++++++++++++++++++-
1 file changed, 22 insertions(+), 1 deletion(-)

diff --git a/eik_containers.mdwn b/eik_containers.mdwn @@ -1,4 +1,4 @@ -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. +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 each. 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. @@ -6,3 +6,24 @@ If we want to have a more PMC take on containers, what we need probably looks mo ### Build a new alpine container +While it's possible to use the standard alpine tools to build a system image, somebody has made a [little script](https://github.com/quantum5/alpine-nspawn-install) that deals with a few small annoyances for us. The script is installed in /usr/sbin so you can just: + +'sudo alpine-nspawn-install -d /var/lib/machines/my_pmc_container -p alpine_pkg1 -p some_other_package` + +__TIP:__ systemd-nspawn images are basically just a normal filesystem tree under /var/lib/machines/my_pmc_container. So, in theory, you can do a lot of interaction with the conainer but just having a directory that is writeable from the containing host. + +### Run the container manually and set a root password + + + +### Set up networking + +### Enable the container + +### Connect via ssh + +### Optionally - set up an nginx proxy for public service + +#### References: + +1. Much of this document was based on [this blog post](https://quantum5.ca/2025/03/22/whirlwind-tour-of-systemd-nspawn-containers/)