Skip to content

Podman: Correct Quadlet install mechanism #2294

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Aug 27, 2024
Merged

Podman: Correct Quadlet install mechanism #2294

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 1 addition & 6 deletions docs/gemstones/containers/podman.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -86,12 +86,7 @@ To automatically run the container upon system start or user login, you can add
WantedBy=default.target
```

Then let the generator run again and enable your service:

```bash
systemctl --user daemon-reload;
systemctl --user enable nextcloud.service;
```
As the generated service files are considered transient, they cannot be enabled by systemd. To mitigate this, the generator manually applies installs during generation. This effectively also enables those services files.

Other file types are supported: pod, volume, network, image, and kube. [Pods](https://docs.podman.io/en/latest/markdown/podman-systemd.unit.5.html#pod-units-pod), for instance, can be used to group containers – the generated systemd services and their dependencies (create the pod before the containers) are automatically managed by systemd.

Expand Down
7 changes: 1 addition & 6 deletions docs/guides/containers/podman_guide.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -163,12 +163,7 @@ To automatically run the container upon system start or user login, you can add
WantedBy=default.target
```

Then let the generator run again and enable your service:

```bash
systemctl --user daemon-reload;
systemctl --user enable nextcloud.service;
```
As the generated service files are considered transient, they cannot be enabled by systemd. To mitigate this, the generator manually applies installs during generation. This effectively also enables those services files.

Other file types are supported: pod, volume, network, image, and kube. [Pods](https://docs.podman.io/en/latest/markdown/podman-systemd.unit.5.html#pod-units-pod), for instance, can be used to group containers – the generated systemd services and their dependencies (create the pod before the containers) are automatically managed by systemd.

Expand Down