goroboro/user-documentation
0
0
Fork 0
forked from server/user-documentation
Code Pull requests Activity

Merge pull request 'Fix typographical errors in containerization section' (!196) from brettweir/user-documentation:proofread-containerization into main

Browse source 
Reviewed-on: server/user-documentation#196
Reviewed-by: Peter Boy <pboy@noreply.forge.fedoraproject.org>
This commit is contained in:
Peter Boy 2026-07-15 11:45:26 +00:00
commit 49c141434f
2 changed files with 8 additions and 8 deletions
Download patch file Download diff file Expand all files Collapse all files

10
modules/ROOT/pages/containerization/index.adoc
View file

@ -6,7 +6,7 @@ Peter Boy
// :revremark: a new beginning
:page-aliases: container-an-introduction.adoc
Since some years "Container" are on everyone's lips. It's a prominent subject of public dicsussion. Complete operating systems are rebuilt to serve primarily as runtime environments for containers. And in public discussion "container" are mostly equated with "Docker". It is hard to find software that is not at least also offered as a Docker image. And it didn't take long for the disadvantages of such a monopolization to become apparent, e.g. in the form of serious security risks.
For several years, "Container" has been on everyone's lips. It's a prominent subject of public discussion. Complete operating systems are rebuilt to serve primarily as runtime environments for containers. And in public discussion "container" are mostly equated with "Docker". It is hard to find software that is not at least also offered as a Docker image. It didn't take long for the disadvantages of such a monopolization to become apparent, e.g. in the form of serious security risks.
As we learn time and time again, one size does not fit all. A number of the advantages of containerization are widely agreed upon. But the needs and requirements in IT are so diverse that not all of them can be optimally realized by one implementation. Therefore, there are alternative container implementations with different application profiles. And containerization is not always helpful either.
@ -14,7 +14,7 @@ As we learn time and time again, one size does not fit all. A number of the adva
== Containerization options in Fedora Server
A common feature of all container systems is the sharing of the host kernel and the use of kernel capabilities (e.g. cnames) to achieve a certain mutual isolation and autonomy.
A common feature of all container systems is the sharing of the host kernel and the use of kernel capabilities (e.g. cgroups) to achieve a certain mutual isolation and autonomy.
They differ in implementation, architecture principles, toolset, runtime environment and community. A rough classification is the distinction between "system container" and "application container", roughly determined by the existence and scope of an init system.
@ -36,10 +36,10 @@ Its characteristics are
* Application container
* Dependent on a daemon with ROOT privileges
* Huge trove of pre-built containers for all sorts of software
* Huge trove of pre-built containers for all sorts of software
* Mixture of a free community edition and a commercial product
Docker releases it own Community Edition for various distributions. Therefore there is *no native support* for Fedora Server, but a *vendor repository* maintained for Fedora.
Docker releases its own Community Edition for various distributions. Therefore, there is *no native support* for Fedora Server, but a *vendor repository* is maintained for Fedora.
=== LXC (libvirt)
@ -73,7 +73,7 @@ Its characteristics are
* Complete versatile toolset, including container images and active supportive community.
* Free open source software
LXD is *not natively supported* by Fedora Server, but there is a *COPR project* available, Additionally there is *vendor support* for Fedora by a third party package manager.
LXD is *not natively supported* by Fedora Server, but there is a *COPR project* available, and there is *vendor support* for Fedora by a third-party package manager.
=== systemd-nspawn container

6
modules/ROOT/pages/containerization/systemd-nspawn-setup.adoc
View file

@ -16,7 +16,7 @@ But of course a container can also be operated with other variations of a networ
1. *Create a container storage area*
+
The systemd-nspawn tools like machinctl look for containers in `/var/lib/machines` first. This directory is also created during the installation of the programs if it does not exist.
The systemd-nspawn tools like machinectl look for containers in `/var/lib/machines` first. This directory is also created during the installation of the programs if it does not exist.
+
Following the Fedora server storage scheme, create a logical volume, create a file system and mount it to `/var/lib/machines`. The tools can use BTRFS properties, so this can be used as a filesystem in this case.
If you don't want to follow the Fedora Server rationale, skip this step.
@ -31,7 +31,7 @@ If you don't want to follow the Fedora Server rationale, skip this step.
(insert)
/dev/mapper/{VGNAME}-machines /var/lib/machines auto 0 0
# mount -a
# mount -a
----
2. *Check and, if necessary, correct the SELinux labels*
+
@ -122,7 +122,7 @@ First create a separate CentOS repository file (e.g. /root/centos.repo) and impo
----
+
This installs 165 packages that occupy 435 M in the file system.
The message: `install-info: File or directory not found for /dev/null` appears several times. The cause is that the `/dev/` file system is not yet initialized at this point. You may savely ignore the message.
The message: `install-info: File or directory not found for /dev/null` appears several times. The cause is that the `/dev/` file system is not yet initialized at this point. You may safely ignore the message.
=== 2.2 Configuration and commissioning of a system container