wdevs/unitdore
5
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 8 Wiki Activity

Improve unit generation for docker, podman, scripts and programs #4

New Issue
Closed
opened 2026-04-03 13:57:12 +00:00 by sgcommand · 0 comments
sgcommand commented 2026-04-03 13:57:12 +00:00
Member
Copy Link
Copy Source

The current generator covers basic container start/stop. Expand it to properly handle each runtime type.

Docker

  • Depend on docker.service: Requires=docker.service / After=docker.service
  • Handle docker compose as a runtime option

Podman

  • Depend on podman.socket where appropriate
  • Support podman pods (not just containers)
  • Handle rootless linger: warn if loginctl enable-linger <user> has not been run

Scripts / Programs

  • New runtime type: exec — runs an arbitrary script or binary directly
  • ExecStart set from command field, no container wrapper
  • Useful for managing non-container services alongside containers in the same config
  • Example:
- name: myworker
  runtime: exec
  command: /opt/myapp/worker.sh
  order: 3
  enabled: true

General

  • Type=forking option for containers that daemonise themselves
  • TimeoutStopSec configurable per unit
  • EnvironmentFile support
The current generator covers basic container start/stop. Expand it to properly handle each runtime type. ## Docker - Depend on `docker.service`: `Requires=docker.service` / `After=docker.service` - Handle `docker compose` as a runtime option ## Podman - Depend on `podman.socket` where appropriate - Support podman pods (not just containers) - Handle rootless linger: warn if `loginctl enable-linger <user>` has not been run ## Scripts / Programs - New runtime type: `exec` — runs an arbitrary script or binary directly - `ExecStart` set from `command` field, no container wrapper - Useful for managing non-container services alongside containers in the same config - Example: ```yaml - name: myworker runtime: exec command: /opt/myapp/worker.sh order: 3 enabled: true ``` ## General - `Type=forking` option for containers that daemonise themselves - `TimeoutStopSec` configurable per unit - `EnvironmentFile` support
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Compat/Breaking
Breaking change that won't be backward compatible
 Kind/Bug
Something is not working
 Kind/Documentation
Documentation changes
 Kind/Enhancement
Improve existing functionality
 Kind/Feature
New functionality
 Kind/Security
This is security issue
 Kind/Testing
Issue or pull request related to testing
Priority
Critical
1
The priority is critical
Priority
High
2
The priority is high
Priority
Medium
3
The priority is medium
Priority
Low
4
The priority is low
Reviewed
Confirmed
1
Issue has been confirmed
Reviewed
Duplicate
2
This issue or pull request already exists
Reviewed
Invalid
3
Invalid issue
Reviewed
Won't Fix
3
This issue won't be fixed
Status
Blocked
1
Something is blocking this issue or pull request
Status
Need More Info
2
Feedback is required to reproduce issue or to continue work
Status
Abandoned
3
Somebody has started to work on this but abandoned work
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
hein (Hein) root sam sgcommand (SG Command) warkanum (Warky)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: wdevs/unitdore#4