Skip to content
Merged
Changes from all commits
Commits
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
10 changes: 9 additions & 1 deletion docs/build-install/containers.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ Its command-line interface (CLI) closely mirrors Docker’s, providing a consist

## Preliminary step: configuring Podman's storage

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:
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:

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

You can use

```bash
podman info | grep -A 2 "store:"
```

to check that the correct `storage.conf` file is used by Podman (`store:configFile` field).

## Building images with Podman

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):
Expand Down