Replies: 1 comment 1 reply
-
Hi, I'm trying to understand the use case. IIUC the sole purpose of the wallabag service is building the image. Am I correct? If yes, what I think you could possibly do is manually write this specific service (as you did) and set it as a dependency for the PHP and Caddy ones. I did have a vision of expanding the |
Beta Was this translation helpful? Give feedback.
1 reply
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'm trying to migrate wallabag to quadlet. Before quadlet, I had 5 systemd services.
I manually replaced
ExecStart
to usepodman create
.Type=oneshot
andRemainAfterExit=yes
were added too. My Containerfile looked something like this:Caddy needs access to wallabag files so they are mounted like this:
--mount type=image,src=wallabag,dst=/usr/share/wallabag,rw=true
--volumes-from wallabag
for the bind mountsPhp also need access to the files so they're also mounted here:
--mount type=image,src=wallabag,dst=/usr/share/wallabag,rw=true
--volumes-from wallabag
for the bind mountsNow my dilemma is running
wallabag
container. I don't see any option in quadlet that allows me to usepodman create
instead ofpodman run
. The container doesn't have asleep
command I can use to keep it running.So I tried to merge wallabag and php-fpm containers into one but realized caddy needs access to the files too. I would need to install caddy, php-fpm and wallabag into one container. I didn't like that idea. I tried to create a systemd drop-in file like this:
But t doesn't remove the
ExecStart=podman run ...
line.I'v ran out of ideas on how to proceed with this. Any help would be appreciated.
Beta Was this translation helpful? Give feedback.
All reactions