permacomputing

commit f6511f7da89d852815cd9c9b58bfa1435e69a060
parent bc69f022cbe8870bf9fac590b4f464ec1a3fc4c1
Author: brendan <brendan@web>
Date:   Mon,  9 Mar 2026 10:38:37 +0100


Diffstat:
M
eik_containers.mdwn
 | 
4
++--

1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/eik_containers.mdwn b/eik_containers.mdwn
@@ -8,9 +8,9 @@ If we want to have a more PMC take on containers, what we need probably looks mo
 
 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`
+`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.
+__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 by just having a directory that is writeable from the containing host.
 
 ### Run the container manually and set a root password