q

Author: DnFreddie

Articles/02-Systemd-Containers/foreground.sh

@@ -1,3 +1,2 @@
 su  ubuntu
 cd ~
-podman build -t try-me /home/ubuntu/quadlet

Articles/02-Systemd-Containers/step1/text.md

@@ -1,43 +1,70 @@
+To enhance your Killercoda lab scenario, let's integrate Podman's Quadlet feature to manage containers as systemd services. This approach aligns with Red Hat's methodologies and leverages systemd for container orchestration.
 
+## **Step 1: Build the Container Image**
 
-Ok, first let's examine whether we have some images on the machine that we
-can turn into systemd services.
+First, ensure you have the necessary files in the `~/quadlet` directory, including the `Dockerfile`. Build the image using Podman:
 
 ```bash
- podman images
-```{exec}
+podman build -t try-me ~/quadlet
+```
 
-Oh, actually, we have something! It's called **try-me**.
 
-We don't know what it's doing.
-Fortunately, the previous colleague left instructions on how to deploy them in a
-**Docker Compose file**, so we don't have to worry too much.
+## **Step 2: Verify Available Images**
 
-Unfortunately, we are the **Red Hat team**, so we use **Podman** instead.
-Maybe there will be something interesting.
+After building, confirm the presence of the `try-me` image:
 
-Let's examine the **Docker Compose file**:
+```bash
+podman images
+```
+
+
+### **Step 3: Review the Docker Compose File**
+
+Although your colleague provided a Docker Compose file, we'll translate its configurations to Quadlet for systemd integration. Examine the file to understand the service requirements:
 
 ```bash
 less docker-compose.yml
-```{exec}
-Ok, so we've got it—no need to worry.
-We need the service that
+```
+
+
+**Service Requirements Identified:**
+
+- Mounts `/test` directory
+
+- Exposes port `8000`
 
-Requiers mounts /test
-* It has to be run on port 8000
-* it needs to be preseinatnt
-* And i has to execute
-* serve  to properly use the conaienr
+- Requires persistent storage
 
-Ok but how to acctualy do that we know that redhat enables us to do that
-wihtout generating it based on this file but how to check
-As i rembermer the quadlet was avaible at verison 4.4 > so mayb podman -V
-Or even easier just type man quadlet
-There u have the table of options at the end of the set
+- Executes the `serve` command
 
+**Step 4: Implement Quadlet for systemd Integration**
 
+Quadlet simplifies running Podman containers under systemd by using dedicated unit files. To utilize Quadlet, create a `.container` file describing your service. For example:
 
-if u evere feel stuck therse an option for u to
+```ini
+[Unit]
+Description=Try-Me Container
 
+[Container]
+Image=localhost/try-me:latest
+Exec=serve
+Mount=/test:/test
+Port=8000:8000
+[Install]
+WantedBy=multi-user.target
+```
+
+
+
+Save this file as `try-me.container` in the appropriate systemd directory, typically `/etc/containers/systemd/`. This configuration ensures that systemd manages the container, maintaining consistency with Red Hat's practices. citeturn0search6
+
+**Step 5: Enable and Start the Service**
+
+Reload systemd to recognize the new service, then enable and start it:
+
+```bash
+systemctl --user daemon-reload
+systemctl --user enable try-me.service
+systemctl --user start try-me.service
+```