Hello Guys,

This possibility was offered in Zabbix Forum using the built-in Docker template  as workaround

1. su - podman
   $ systemctl --user enable podman.service
   $ systemctl --user start podman.service

Because of permissions

1. usermod -G podman zabbix
2. chmod 750 /run/user/$(id -u podman)
3. echo "Plugins.Docker.Endpoint=unix://run/user/$(id -u podman)/podman/podman.sock" >> /etc/zabbix/zabbix_agent2.d/plugins.d/docker.conf
4. systemctl restart zabbix-agent2.service

please add native template

Any news about this?
It would be good to have a native template for Podman container monitoring instead of a workaround with a Docker template.

I don't think this is an optimal solution, rickkbarbosa as it requires additional steps to allow Zabbix to monitor user containers.

I've created this discussion on GitHub that shows some of these steps. Even if you do this, the permissions for the temporary directories created for Podman will be lost after a reboot.

Also, the current Docker plugin configuration file only allows for one socket at a time. So, if you have multiple users, each with their own Pod, you can only monitor one user at a time with the docker plugin.

Unless you use custom parameters or an external check, for now I don't see how to monitor multiple user containers on the same host.

Hey Folks,

I've added a template to Zabbix's community repository (currently a pull request, so I'm waiting for a maintainer to approve.) Pull Req #453 (Adding community rootless podman monitoring template with clear instructions. by MRedbourne-BPSI · Pull Request #453 · zabbix/community-templates)

The changes made are permanent and will survive a reboot. Essentially, we're using sudo to execute the podman commands as other users. The sudo changes are specific in nature, so they should pose a relatively small security footprint. If you have different users on different servers, duplicate the template. If you have multiple users on a single server, you will need to duplicate the master items (podman.ps) and delineate by doing something like "podman.ps.Bob", "podman.ps.Jane", then duplicate out the discovery items and various prototypes. The trigger section is weak right now (Offline, Not Running, Recently Restarted). If you have other ideas, I'm all ears.

Edit: Just to be clear - this is meant for rootless monitoring in a RHEL environment (or RHEL-equivalent such as Rocky, Alma, CentOS, or Fedora). There is also an TCP-based API available that may work better in the future. 

I don't think Zabbix will ever really have a "native" template for this. They would probably need to ship the agent config in a seperate RPM to deal with the sudo permissions. Podman to my knowledge that allows a given suer to show all pods, just the ones they started. This goes for root as well, hence why the sudo permissions given are specific to a given user.