leviathonbeast/lldap
1
0
Fork 0
mirror of https://github.com/lldap/lldap.git synced 2026-03-31 15:07:48 +01:00
Code Issues Packages Projects Releases Wiki Activity

example_configs: fix the quadlet readme

Browse Source 
Several "podman" command should have been "systemctl" from the start.
This commit is contained in:
Alexandre Foley
2025-09-04 16:23:12 -04:00
committed by GitHub
parent 775c5c716d
commit c68f9e7cab
1 changed files with 6 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files
example_configs/podman-quadlets/readme.md
+6 -6
View File
@@ -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