inmanta-module-podman
This package is an adapter that is meant to be used with the inmanta orchestrator: https://docs.inmanta.com
Features
This module allows to manage podman resources, on a unix host. It contains the following resources:
podman::Network: to manage a podman network (subnets, routes, dns, driver, labels, options, ...).podman::NetworkDiscovery: to discover existing podman networks owned by a user on a host.podman::Pod: to manage a podman pod, including its networking, port publishing, id mapping and shared resources.podman::Container: to manage a podman container (image, command, environment, volumes, networks, healthcheck, security label, resource limits, auto-update, ...).podman::Image,podman::ImageFromRegistryandpodman::ImageFromSource: to make sure a container image is present on a host, either pulled from a registry or built from aContainerfile.podman::ImageDiscovery: to discover existing container images owned by a user on a host.podman::AutoUpdate: to configure the podman auto-update service for a given user.podman::services::SystemdContainer,podman::services::SystemdPodandpodman::services::SystemdAutoUpdate: to wrap a container, a pod or the auto-update service into a systemd service. These services can either be generated as plain systemd unit files (calling thepodmancli) or as quadlet unit files.
Example
The following example shows how to run a container as a systemd service, using a quadlet unit file. The container is a simple nginx web server, exposing its port 80 on the host port 8080.
import mitogen
import podman
import podman::container_like
import podman::services
import std
host = std::Host(
name="localhost",
os=std::linux,
via=mitogen::Local(),
)
# Make sure the container image is present on the host
image = podman::ImageFromRegistry(
host=host,
name="docker.io/library/nginx:latest",
)
# Define the container
web = podman::Container(
host=host,
name="nginx-web",
image=image.name,
publish=[
podman::container_like::Publish(host_port="8080", container_port="80"),
],
)
# Wrap the container into a systemd service, using a quadlet unit file
podman::services::SystemdContainer(
container=web,
state="running",
enabled=true,
systemd_unit_dir="/etc/systemd/system",
systemd_container_dir="/etc/containers/systemd",
quadlet=true,
)
Find more examples in the tests folder of this module!
1 maintainer
Metadata
1 maintainer
Release files for inmanta-module-podman 1.13.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| inmanta_module_podman-1.13.3.tar.gz | 38.7 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| inmanta_module_podman-1.13.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 83.3 kB
Release files / inmanta_module_podman-1.13.3.tar.gz
| Download URL | inmanta_module_podman-1.13.3.tar.gz |
|---|---|
| Size | 38.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6344e50fb8425c83fafb659d64f49891ae77cab34e21079ce666cba30f7f6f7c
|
|
BLAKE2b-256 checksum How to use checksums |
05aa40641394588fda8bed9bec33405bd8997e7c427899e98ac29ea686808ffd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 18, 2026.
Transparency logRelease files / inmanta_module_podman-1.13.3-py3-none-any.whl
| Download URL | inmanta_module_podman-1.13.3-py3-none-any.whl |
|---|---|
| Size | 44.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
90609b5140f39367741e74b4e19f122c956ce6cd26b3fa552685d7671b0796ae
|
|
BLAKE2b-256 checksum How to use checksums |
8b1f069fedbee9e912f2e0d8f0956ed9d9e7758990f157879012e696ecb5fdca
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 18, 2026.
Transparency logSecurity for inmanta-module-podman 1.13.3
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for inmanta_module_podman-1.13.3.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 18, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
