-
Notifications
You must be signed in to change notification settings - Fork 95
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
Run the SOCI snapshotter with systemd #660
Comments
@ollypom starting soci as a normal process on boot proved to be an issue with the Windows implementation of Finch, so we opted to pivot to starting soci as a systemd service as part of that effort. See finch/pkg/config/lima_config_applier.go Lines 39 to 46 in 998989a
which is included in #649 We can opt to either port that commit over to |
Issue #, if available: #660 and probably #661 *Description of changes:* - Run SOCI as a systemd service - Ported from #649, which still needs more time before we can merge it *Testing done:* - e2e/unit tests - [x] I've reviewed the guidance in CONTRIBUTING.md #### License Acceptance By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license. --------- Signed-off-by: Justin Alvarez <[email protected]>
Fixed by #667. |
What is the problem you're trying to solve?.
Today we are running the SOCI snapshotter as a background process. Could we switch to running the SOCI snapshotter as a systemd service? Among many other benefits, it would help centralize soci snapshotter logs into journald. The SOCI snapshotter project already provides an example systemd file.
We also are already running the stargz snapshotter with systemd in Finch (Another outstanding question here is should we be? considering we don't expose stargz in the Finch configuration file).
Describe the feature you'd like
Could we switch to running the SOCI snapshotter as a systemd service?
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: