Support for systemd user services
- Dominant language
- Go
- Stars
- 974
- Forks
- 296
- Avg merge
- 6d 14h
- Merged PRs (30d)
- 9
Description
I'm using rootless podman containers when possible (configured with podman generate systemd) and having them always run by enabling linger on my account. Transitioning to a FCOS setup using fcct was easily possible, but I'm forced to use a awkward workaround.
I use trees to import ~/.config/systemd/user and then create a service on first boot that relabels ~/ to the correct owner. My setup would be easier written using the systemd sugar in fcct if user-services were supported.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the open linked pull request #1303 and the issue's description of systemd user services, fcct, and rootless Podman. Determine how user-service support should fit the existing systemd sugar, then verify that the configuration can express the described setup without the workaround.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- operating-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100