Capitalize Warewulf in userdocs where appropriate

Signed-off-by: Jonathon Anderson <janderson@ciq.co>
This commit is contained in:
Jonathon Anderson
2023-02-21 09:18:07 -07:00
parent 1a59080a99
commit ed7f817932
4 changed files with 9 additions and 9 deletions

View File

@@ -68,8 +68,8 @@ The above is just an example. Consideration should be done before doing it this
Syncuser Syncuser
-------- --------
At import time warewulf checks if the names of the users on the host match the users and UIDs/GIDs in the imported container. If there is mismatch, the import command will print out a warning. At import time Warewulf checks if the names of the users on the host match the users and UIDs/GIDs in the imported container. If there is mismatch, the import command will print out a warning.
By setting the ``--syncuser`` flag you advise warewulf to try to syncronize the users from the host to the container, which means that ``/etc/passwd`` and ``/etc/group`` of the imported container are updated and all the files belonning to these UIDs and GIDs will also be updated. By setting the ``--syncuser`` flag you advise Warewulf to try to syncronize the users from the host to the container, which means that ``/etc/passwd`` and ``/etc/group`` of the imported container are updated and all the files belonning to these UIDs and GIDs will also be updated.
A check if the users of the host and container matches can be triggered with the ``syncuser`` command. A check if the users of the host and container matches can be triggered with the ``syncuser`` command.
@@ -177,7 +177,7 @@ You can use these as starting points and adding any additional steps you want in
Building A Container Using Podman Building A Container Using Podman
-------------------------------------- --------------------------------------
You can also build a container using podman via a `Dockerfile`. For this step the container must be exported to a tar archive, which then can be imported to warewulf. The following steps will create an openSUSE Leap container and import it to Warewulf: You can also build a container using podman via a `Dockerfile`. For this step the container must be exported to a tar archive, which then can be imported to Warewulf. The following steps will create an openSUSE Leap container and import it to Warewulf:
.. code-block:: bash .. code-block:: bash

View File

@@ -56,7 +56,7 @@ Turn off default network dhcp on server master1
sudo virsh net-start default sudo virsh net-start default
Build and install warewulf on wwdev Build and install Warewulf on wwdev
=================================== ===================================
.. code-block:: bash .. code-block:: bash
@@ -125,4 +125,4 @@ Build and install warewulf on wwdev
sudo wwctl server start sudo wwctl server start
sudo wwctl server status sudo wwctl server status
Boot your node and watch the bash and the output of the Warewulfd process Boot your node and watch the bash and the output of the Warewulfd process

View File

@@ -28,7 +28,7 @@ I have VirtualBox running on my desktop.
# Next attach the second Network adapter #2 to the NAT Network and you should be able to choose # Next attach the second Network adapter #2 to the NAT Network and you should be able to choose
# the 'wwnatnetwork' created above in step #1 from the drop down list. # the 'wwnatnetwork' created above in step #1 from the drop down list.
3. Build and install warewulf on wwdev 3. Build and install Warewulf on wwdev
.. code-block:: console .. code-block:: console
@@ -135,7 +135,7 @@ I have VirtualBox running on my desktop.
sudo wwctl server start sudo wwctl server start
sudo wwctl server status sudo wwctl server status
4. Create a new guest VM instance inside the VirtualBox to be the warewulf client/compute node. Under the system configuration make sure to select the optical and network options only for the boot order. The default iPXE used by VirtualBox does not come with bzImage capability which is needed for warewulf. Download the ipxe.iso available at ipxe.org and mount the ipxe.iso to the optical drive. Enable one Network adapter for this VM and assign it to the NAT Network created in step #1 above. 4. Create a new guest VM instance inside the VirtualBox to be the Warewulf client/compute node. Under the system configuration make sure to select the optical and network options only for the boot order. The default iPXE used by VirtualBox does not come with bzImage capability which is needed for Warewulf. Download the ipxe.iso available at ipxe.org and mount the ipxe.iso to the optical drive. Enable one Network adapter for this VM and assign it to the NAT Network created in step #1 above.
.. code-block:: console .. code-block:: console
@@ -144,4 +144,4 @@ I have VirtualBox running on my desktop.
# VM Settings -> Storage and mount the above download ipxe.so to the Optical Drive. # VM Settings -> Storage and mount the above download ipxe.so to the Optical Drive.
# VM Settings -> Network Enable adapter #1, attach to 'Nat Network' and choose 'wwnatnetwork' from the drop down list. # VM Settings -> Network Enable adapter #1, attach to 'Nat Network' and choose 'wwnatnetwork' from the drop down list.
Boot your node and watch the console and the output of the Warewulfd process Boot your node and watch the console and the output of the Warewulfd process

View File

@@ -12,7 +12,7 @@ docker build -t docker.psi.ch:5000/debian:buster-slim .
docker push docker.psi.ch:5000/debian:buster-slim docker push docker.psi.ch:5000/debian:buster-slim
``` ```
### import docker container into warewulf ### import docker container into Warewulf
```bash ```bash
wwctl container import docker://docker.psi.ch:5000/debian:buster-slim debian-10:slim wwctl container import docker://docker.psi.ch:5000/debian:buster-slim debian-10:slim