You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/guides/containers/podman_guide.md
+26-26Lines changed: 26 additions & 26 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -163,22 +163,22 @@ To automatically run the container upon system start or user login, you can add
163
163
WantedBy=default.target
164
164
```
165
165
166
-
Then let the generator run again, and enable your service:
166
+
Then let the generator run again and enable your service:
167
167
168
168
```bash
169
169
systemctl --user daemon-reload;
170
170
systemctl --user enable nextcloud.service;
171
171
```
172
172
173
-
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 theirs dependencies (create the pod before the containers) are automatically managed by systemd.
173
+
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.
174
174
175
175
### Using `podman generate systemd`
176
176
177
177
Podman additionally provides the `generate systemd` subcommand. Use this subcommand to generate `systemd` service files.
178
178
179
179
!!! warning
180
180
181
-
`generate systemd` is now deprecated and will not receive further features. Usage of Quadlet is recommended.
181
+
`generate systemd` is now deprecated and will not receive further features. The usage of Quadlet is recommended.
182
182
183
183
Let us now do it with Nextcloud. Run:
184
184
@@ -207,7 +207,7 @@ When your system reboots, Nextcloud will restart in Podman.
207
207
208
208
## Containerfiles
209
209
210
-
A Containerfile is a file used by Podman to create container images. Containerfiles use the same syntax as Dockerfiles, so you can build your container images with Podman like you would with Docker.
210
+
A Containerfile is a file used by Podman to create container images. Containerfiles use the same syntax as Dockerfiles, so you can build your container images with Podman like you would with Docker.
You can add the `--rm` switch to automatically delete the container once it stopps.
335
+
You can add the `--rm` switch to automatically delete the container once it stops.
336
336
337
337
If you relaunch the build process, `podman` will use a cache at each step of the build:
338
338
@@ -377,32 +377,32 @@ podman system prune -a -f
377
377
378
378
## Pods
379
379
380
-
Pods are a way to group container together. Containers in a pod share some settings, like mounts, resource allocations or port mappings.
380
+
Pods are a way to group containers together. Containers in a pod share some settings, like mounts, resource allocations, or port mappings.
381
381
382
382
In Podman, you manage pods using the `podman pod` subcommand, similar to many Podman commands, to control containers:
383
383
384
384
| Command | Description |
385
385
|-- |-- |
386
-
| clone |Create a copy of an existing pod. |
387
-
| create |Create a new pod. |
388
-
| exists |Check if a pod exists in local storage. |
386
+
| clone |Creates a copy of an existing pod. |
387
+
| create |Creates a new pod. |
388
+
| exists |Checks if a pod exists in local storage. |
389
389
| inspect | Display information describing a pod. |
390
-
| kill |Kill the main process of each container in one or more pods. |
391
-
| logs |Display logs for pod with one or more containers. |
392
-
| pause |Pause one or more pods. |
393
-
| prune |Remove all stopped pods and their containers. |
394
-
| ps |Print out information about pods. |
395
-
| restart |Restart one or more pods. |
396
-
| rm |Remove one or more stopped pods and containers. |
397
-
| start |Start one or more pods. |
398
-
| stats |Display a live stream of resource usage stats for containers in one or more pods. |
399
-
| stop |Stop one or more pods. |
400
-
| top |Display the running processes of containers in a pod. |
401
-
| unpause |Unpause one or more pods. |
402
-
403
-
Containers grouped into a pod can access each other by using localhost. This is usefull, for instance, when setting up Nextcloud with a dedicated database like postgres. Nextcloud can access the database, but the database does not need to be accessible from outside the containers.
404
-
405
-
To create a pod containing Nextcloud and a dedicated database run:
390
+
| kill |Kills the main process of each container in one or more pods. |
391
+
| logs |Displays logs for pod with one or more containers. |
392
+
| pause |Pauses one or more pods. |
393
+
| prune |Removes all stopped pods and their containers. |
394
+
| ps |Prints out information about pods. |
395
+
| restart |Restarts one or more pods. |
396
+
| rm |Removes one or more stopped pods and containers. |
397
+
| start |Starts one or more pods. |
398
+
| stats |Displays a live stream of resource usage stats for containers in one or more pods. |
399
+
| stop |Stops one or more pods. |
400
+
| top |Displays the running processes of containers in a pod. |
401
+
| unpause |Unpauses one or more pods. |
402
+
403
+
Containers grouped into a pod can access each other by using localhost. It is useful, for instance, when setting up Nextcloud with a dedicated database like Postgres. Nextcloud can access the database, but the database does not need to be accessible from outside the containers.
404
+
405
+
To create a pod containing Nextcloud and a dedicated database, run the following:
0 commit comments