From c68f9e7cabcaaa894b1a405d7bb4da1e0273fae6 Mon Sep 17 00:00:00 2001 From: Alexandre Foley Date: Thu, 4 Sep 2025 16:23:12 -0400 Subject: [PATCH] example_configs: fix the quadlet readme Several "podman" command should have been "systemctl" from the start. --- example_configs/podman-quadlets/readme.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/example_configs/podman-quadlets/readme.md b/example_configs/podman-quadlets/readme.md index bdd5649..87801eb 100644 --- a/example_configs/podman-quadlets/readme.md +++ b/example_configs/podman-quadlets/readme.md @@ -31,13 +31,13 @@ Starting `lldap.service` will start all the other services, but stopping it will - At this point, you should be able to start the container. - Test this with: ```bash - $ podman --user daemon-reload - $ podman --user start lldap - $ podman --user status lldap + $ systemctl --user daemon-reload + $ systemctl --user start lldap + $ systemctl --user status lldap ``` - Assuming it launched correctly, you should now stop it again. ```bash - $ podman --user stop lldap + $ systemctl --user stop lldap ``` - Make any adjustments you feel are necessary to the network files. - Now all that's left to do is the [bootstrapping process](../bootstrap/bootstrap.md#docker-compose): @@ -45,8 +45,8 @@ Starting `lldap.service` will start all the other services, but stopping it will - Toward the end of the container section, uncomment the lines in `lldap.container` regarding the bootstrap process. - Start the container: ```bash - $ podman --user daemon-reload - $ podman --user start lldap + $ systemctl --user daemon-reload + $ systemctl --user start lldap ``` - Attach a terminal to the container, and run `bootstrap.sh`: ```bash