Quadlet: Prepend ExecStart podman
option?
#26130
Unanswered
jamespeterschinner
asked this question in
Q&A
Replies: 1 comment
-
Yes, currently Quadlet runs only podman without the ability to prepend it with anything else and I'm not sure if this will change. Having said that I would like to better understand what you are running and see if we can find a solution that will allow you to still use Quadlet as is. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I may be uninformed, but AFIAK when creating
<thing>.container
files for podman quadlet, there is no option to prepend something to the start of theExecStart=/user/local/bin/podman run ...
command?The reason I ask and want this capability is to allow me to inject secrets via something like vault agent. Something like that feels to be a great fit (unless system-creds can somehow fill that requirement). Although using vault agent specifically would mean taking the generated
ExecStart
output and placing it into another config file (so not the exact use case I describe).Prior to quadlet I was constructing my systemd
.service
files manually (and incorrectly it seems after seeing quadlets output) but I really need/want thisExecStart
customization.My current thinking is as follows.
QUADLET_UNIT_DIRS=$(pwd) ./quadlet -dryrun
(using an undocumented env var for CI purposes) and then postprocessing before coping said unit file. (Basically looses all the benefit of getting automatic updates from podman)PODMAN
env var so could potentially stuff other commands into this (but no idea how to have said VAR set during system boot)Anyway interested to hear thoughts on this. Thanks!
Beta Was this translation helpful? Give feedback.
All reactions