You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Instead of running a static binary on the host run a container managed by systemd
Why do we need it?
A compromise between kubernetes, and running binaries on the host seems like a nice compromise to use podman/docker. There's also the containers module on Ansible though not sure if the project wants to be dependant on it.
Hi @SuperQ thanks for the super quick response. That's exactly what I think is best. Instead just relying on systemd to ensure the container is started on boot(from docker/podman). Like the article I linked above. I'd be happy to give a hand.
What is missing?
Instead of running a static binary on the host run a container managed by systemd
Why do we need it?
A compromise between kubernetes, and running binaries on the host seems like a nice compromise to use podman/docker. There's also the containers module on Ansible though not sure if the project wants to be dependant on it.
https://podman.io/blogs/2018/09/13/systemd.html
Anything else we need to know?:
This can be useful for adding support for distros like Fedora Atomic, and OpenSUSE MicroOS, or and "atomic" host
The text was updated successfully, but these errors were encountered: