RHEL9 install broken.

[Shakahs]

The official installation instructions do not work.
After running sudo yum -y install nomad-driver-podman and restarting both Podman and Nomad, Nomad does not find the Podman driver.

Manually downloading the current dev release from Github and placing it in the plugins directory also does not work.

[Juanadelacuesta]

Hi @Shakahs!
Thank you for reaching out, to help us pint point your problem, can you share your nomad agent configuration?

For the nomad agent to pick up on plugins, it needs to know where to look for them, you can do this by:

1. Filling the plugin_dir on the agent configuration with the absolute path of the directory where the plugin is, or pass it with the flag --plugin-dir when running the nomad agent command.
2. Moving your plugin to the default plugins directory nomad will create if none is provided.

You can use rpm -ql nomad-driver-podman to determine where was the plugin stored by yum

Also you need to make sure that your machine has podman installed and running and it is accesible to Nomad. By default the agent will assume you are running it "rootful" and will look for the podman socket at unix:///run/podman/podman.sock as stated on the documentation, if you are running it rootless, updated the socket_path inside the driver configuration:

plugin "nomad-driver-podman" {
    config {
        socket_path= "unix://run/user/1000/podman/podman.sock"
    }
}

Finally if you are seeing the following line on your agent logs:
[WARN] agent.plugin_loader: plugin not referenced in the agent configuration file, loading skipped: plugin_dir=/home/ec2-user/plugin plugin=nomad-driver-podman

it means Nomad is seeing the driver but since it is not configured on the client, it is skipped.

Please let us know if this helps!

[p1u3o]

I ran into this, I just symlinked the plugin into the plugin directory so updates installed by DNF still work

$ ln -s /usr/bin/nomad-driver-podman /opt/nomad/plugins/

Maybe it should be suggested in the README

[Klaas-]

I'd guess this only happens on upgrades, see PR #448 for details

[p1u3o]

I'd guess this only happens on upgrades, see PR #448 for details

In my case it was not an upgrade.

[Klaas-]

I'd guess this only happens on upgrades, see PR #448 for details

In my case it was not an upgrade.

Hi,
if you had to do "ln -s /usr/bin/nomad-driver-podman /opt/nomad/plugins/" in order to fix it, it was most likely an upgrade, not an install. If you install it that symlink will be created via the post install rpm script: https://github.com/hashicorp/nomad-driver-podman/blob/main/.release/linux/postinst if that did not work you should see an error during the installation.
On upgrades it will be removed by removing the old package via https://github.com/hashicorp/nomad-driver-podman/blob/main/.release/linux/postrm

[Juanadelacuesta]

@p1u3o Have you been able to run the podman plugin?

[p1u3o]

@Juanadelacuesta Yes after creating a symlink.

I'm 99% sure in my case it wasn't an upgrade though, the VM I tested it on only had the Docker plugin and didn't even have Podman installed.

However /opt/nomad/data/plugins did not exist until I made it.

[Klaas-]

Maybe there is an additional problem with the post install script. But from looking at it briefly I would say I expect it to be executed on an rpm install. It should create the dir and the softlink. If it doesn't work the script should fail and it should produce an error during the dnf install phase :)