-has to do.
-
-Many container platforms offer additional features not to be discussed
-here, like downloading and unpacking a file system image from the
-internet, or supplying the root file system for the container by other
-means, for example by creating an LVM snapshot of a master image.
-LXC is a comparably simple container platform which can be used to
-start a single daemon in a container, or to boot a container from
-a root file system as described above. It provides several <code>
-lxc-* </code> commands to start, stop and maintain containers.
-LXC version 1 is much simpler than subsequent versions, and is still
-being maintained, so we only discuss this version of LXC here.
-
-An LXC container is defined by a configuration file in
-the format described in <code> lxc.conf(5)</code>. A <a
-href="#minimal_lxc_config_file"> minimal configuration </a> which
-defines a network device and requests CPU and memory isolation has
-as few as 10 lines (not counting comments). With the configuration
-file and the root file system in place, the container can be started
-by running <code> lxc-start -n $NAME</code>. One can log in to the
-container on the local pseudo terminal or via ssh (provided the sshd
-package is installed). The container can be stopped by executing
-<code> halt </code> from within the container, or by running <code>
-lxc-stop </code> on the host system. <code> lxc-ls </code> and
-<code> lxc-info</code> print information about containers, and <code>
-lxc-cgroup </code> changes the settings of the cgroup associated with
-a container.
-
-The exercises ask the reader to install the LXC package from source,
-and to set up a minimal container running Ubuntu-18.04.
+has to do. </p>
+
+<p> Many container platforms offer additional features not to
+be discussed here, like downloading and unpacking a file system
+image from the internet, or supplying the root file system
+for the container by other means, for example by creating an
+LVM snapshot of a master image. In this section we look at <a
+href="http://people.tuebingen.mpg.de/maan/micoforia/">micoforia</a>,
+a minimalistic container platform to boot a container from an existing
+root file system as described above. </p>
+
+<p> The containers known to micoforia are defined in the single
+<code>~/.micoforiarc</code> configuration file whose format is
+described in <code>micoforia(8)</code>. The <code>micoforia</code>
+command supports various subcommands to maintain containers. For
+example, containers are started with a command such as <code>micoforia
+start c1</code> where <code>c1</code> is the name of the
+container. One can execute a shell running within the container
+with <code>micoforia enter c1</code>, log in to a local pseudo
+terminal with <code>micoforia attach c1</code>, or connect via ssh
+with <code>ssh c1</code>. Of course the latter command only works
+if the network interface and the DNS record get configured during
+container startup and the sshd package is installed. The container can
+be stopped by executing <code>halt</code> from within the container,
+or by running <code>micoforia stop c1</code> on the host system. The
+commands <code>micoforia ls</code> and <code>micoforia ps</code>
+print information about containers and their processes. </p>
+
+<p> The exercises ask the reader to install the micoforia package from
+source, and to set up a minimal container running Ubuntu Linux. </p>
projects / aple.git / blobdiff