Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Southalc podman module doesn't enable service #86

Open
ultrapain1 opened this issue May 21, 2024 · 1 comment
Open

Southalc podman module doesn't enable service #86

ultrapain1 opened this issue May 21, 2024 · 1 comment

Comments

@ultrapain1
Copy link

From the podman v0.6.7 module on forge.puppet.com:

enable
Data type: Boolean

Status of the automatically generated systemd service for the container. Valid values are 'running' or 'stopped'.

Default value: true

There is an issue with the code in container.pp. The variable $service_unit_file is defined as:
${User[$user]['home']}/.config.systemd/user/podman-${container_name}.service

In this code block, you don't specify the full path of the service:
$command_sp @("END"/L)
${systemctl} ${startup} podman-${container_name}.service
${systemctl} ${action} podman-${container_name}.service
| END

This code should be changed to:
${systemctl} ${startup} ${service_unit_file}

@breca
Copy link

breca commented May 24, 2024

Hey, I'm using v0.6.7 (the latest release) in my environment. I can't say I've encountered this issue myself.

I'd expect this sort of thing could happen if a daemon-reload was somehow not executed?

Relevant sections
https://github.com/southalc/podman/blob/0.6.7/manifests/container.pp#L101-L157
https://github.com/southalc/podman/blob/0.6.7/manifests/container.pp#L300-L343

Could you share more details about the your environment and the specific issue you're having? (Debug logs might be good)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants