-
Notifications
You must be signed in to change notification settings - Fork 2
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
db021c1
commit 7aebd4e
Showing
66 changed files
with
331 additions
and
75 deletions.
There are no files selected for viewing
Large diffs are not rendered by default.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Large diffs are not rendered by default.
Oops, something went wrong.
Large diffs are not rendered by default.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,37 @@ | ||
============ | ||
Known issues | ||
============ | ||
|
||
SELinux and IPMI write not working when using two-stage boot | ||
============================================================ | ||
|
||
The dracut implementation of two-stage boot in versions of Warewulf prior to v4.6.0 bypasses the | ||
``wwinit`` process by default, invoking the image's init system directly. While cluster nodes will | ||
often still boot mostly successfully this way, features implemented by wwinit will not complete. In | ||
particular, SELinux relabeling and IPMI write are not executed. | ||
|
||
To ensure that dracut runs the full ``wwinit`` process, pass ``init=/init`` or | ||
``init=/warewulf/wwinit`` on the kernel command line. | ||
|
||
.. code-block:: bash | ||
# wwctl profile set default --kernelargs="init=/init" | ||
Containers are read-only | ||
======================== | ||
|
||
Warewulf v4.5 uses the permissions on a container's ``rootfs/`` to determine a "read-only" state of | ||
the container: if the root directory of the container image is ``u-w``, it will be mounted read-only | ||
during ``wwctl container <exec|shell``, preventing interactive changes to the container image. | ||
|
||
In the past, the root directory was ``u+w``, but Enterprise Linux 9.5 (including Red Hat, Rocky, _et | ||
al._) includes an update to the ``filesystem`` package that marks the root directory ``u-w``. This | ||
causes Warewulf container images to be "read only" by default. | ||
|
||
To mark a Warewulf container as writeable, use `chmod u+w`. | ||
|
||
.. code-block:: bash | ||
# chmod u+w $(wwctl container show rockylinux-9.5) | ||
This behavior is changed in v4.6 to use an explicit ``readonly`` file stored outside of ``rootfs/``. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.