A hook or global (default) options

[hoshsadiq]

Feature request description

I am looking to always add some options to all containers. For my use case, this for local development rather than anything else.

I'd like to be able to specify certain volumes to always be attached to containers. Ideally based on certain criteria. Specifically what I'm trying to achieve is to mount some caching directories so that some things don't have to continually re-download, e.g. apt, apk, etc.

I tend to use containers for lots of testing, e.g. spin up a temporary container (podman run...), install some tools (apk add ...), and then exit the container, only to then do it again not long after.

I'd like to be able to always add a volume to all these containers based on certain criteria such as the container image, tag, etc. This way I can add a cache volume for debian:stable, or alpine: etc.

This is also helpful to be able to do at docker level, as e.g. it would allow for cached packages to so that these things can be done offline if for some reason you don't have internet temporarily.

Suggest potential solution

Maybe some additional config that specifies podman run args that would be inject for all containers. Or a hook system that allows me make changes to the podman run command.

Have you considered any alternatives?

I've considered using a wrapper command that adds the arguments I need, but this doesn't capture things like docker compose.

Additional context

No response

[Luap99]

Hooks already exist via the standard OCI hooks
https://github.com/containers/container-libs/blob/main/common/pkg/hooks/docs/oci-hooks.5.md

podman/docs/source/markdown/podman.1.md

Lines 60 to 74 in 5a0b74b

	#### **--hooks-dir**=*path*
	Each `*.json` file in the path configures a hook for Podman containers. For more details on the syntax of the JSON files and the semantics of hook injection, see `oci-hooks(5)`. Podman and libpod currently support both the 1.0.0 and 0.1.0 hook schemas, although the 0.1.0 schema is deprecated.
	This option may be set multiple times; paths from later options have higher precedence (`oci-hooks(5)` discusses directory precedence).
	For the annotation conditions, libpod uses any annotations set in the generated OCI configuration.
	For the bind-mount conditions, only mounts explicitly requested by the caller via `--volume` are considered. Bind mounts that libpod inserts by default (e.g. `/dev/shm`) are not considered.
	If `--hooks-dir` is unset for root callers, Podman and libpod currently default to `/usr/share/containers/oci/hooks.d` and `/etc/containers/oci/hooks.d` in order of increasing precedence. Using these defaults is deprecated. Migrate to explicitly setting `--hooks-dir`.
	Podman and libpod currently support an additional `precreate` state which is called before the runtime's `create` operation. Unlike the other stages, which receive the container state on their standard input, `precreate` hooks receive the proposed runtime configuration on their standard input. They may alter that configuration as they see fit, and write the altered form to their standard output.
	**WARNING**: the `precreate` hook allows powerful changes to occur, such as adding additional mounts to the runtime configuration. That power also makes it easy to break things. Before reporting libpod errors, try running a container with `precreate` hooks disabled to see if the problem is due to one of the hooks.

containers.conf also already exist to configure default options for all containers.
https://github.com/containers/container-libs/blob/main/common/docs/containers.conf.5.md

I'd like to be able to always add a volume to all these containers based on certain criteria such as the container image, tag, etc. This way I can add a cache volume for debian:stable, or alpine: etc.

That should be possible with hooks reading the metadata they receive I think. containers.conf applies to all and i would be strongly opposed to adding new configs that only trigger on certain condition as the configs today are already very hard to maintain.