-
Notifications
You must be signed in to change notification settings - Fork 475
-
Notifications
You must be signed in to change notification settings - Fork 475
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
Podman Compose Systemd registers an unusable service #753
Comments
Problem is that the systemd unit file assumes that |
Lol, please ignore the two broken pull-requests, my brain is clearly on the fritz this afternoon. |
this should be fixed by merging #772 |
there is no need for #772 because in latest dev in-pod defaults to 1 actually pod-systemd was never part of previous stable, and in-pod is a breaking change that's why it's disabled in latest stable you have two options
|
I just wanted to post a workaround for people using the stable version. You can create a drop-in systemd file with modified
|
While trying to run a podman-compose containing two containers of wireguard and wireguard-ui on my raspberry pi, I went into configuring the restart policy which impies:
The problem is that the service will not start, neither on reboot nor manually:
A more in depth log analisys shows a container with the same name is already existing, even if I did not manually started the compose file:
So I checked the linked systemd file:
I see that containers are generated and started on separated instances, what I've done is creating and starting the up command:
This solved my issues, still this should work out of the box.
Am I doing something wrong?
Cheers
Environment:
The text was updated successfully, but these errors were encountered: