Skip to content

Commit baa5e76

Browse files
authored
Update containers.md (#133)
1 parent 3b4edea commit baa5e76

File tree

1 file changed

+9
-1
lines changed

1 file changed

+9
-1
lines changed

docs/build-install/containers.md

Lines changed: 9 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ Its command-line interface (CLI) closely mirrors Docker’s, providing a consist
66

77
## Preliminary step: configuring Podman's storage
88

9-
The first step in order to use Podman on Alps is to create a valid Container Storage configuration file at `$HOME/.config/containers/storage.conf`, according to the following minimal template:
9+
The first step in order to use Podman on Alps is to create a valid Container Storage configuration file at `$HOME/.config/containers/storage.conf` (or `$XDG_CONFIG_HOME/containers/storage.conf`, if you have `$XDG_CONFIG_HOME` set), according to the following minimal template:
1010

1111
```toml
1212
[storage]
@@ -21,6 +21,14 @@ graphroot = "/dev/shm/$USER/root"
2121
The limitation of this approach is that container images created during a job allocation are deleted when the job ends.
2222
Therefore, the image needs to either be pushed to a container registry or imported by the Container Engine before the job allocation finishes.
2323

24+
You can use
25+
26+
```bash
27+
podman info | grep -A 2 "store:"
28+
```
29+
30+
to check that the correct `storage.conf` file is used by Podman (`store:configFile` field).
31+
2432
## Building images with Podman
2533

2634
The easiest way to build a container image is to rely on a Containerfile (a more generic name for a container image recipe, but essentially equivalent to Dockerfile):

0 commit comments

Comments
 (0)