Hrmmm.  Looking at the logs you provided more (again, I'm not a quadlet 
or systemd expert), I'm wondering if most of the warnings/errors are 
also harmless because I see toward the end:
podman[787]: 2023-05-25 03:01:59.00150107 +0300 EEST m=+0.108624239 
image pull  <redacted>:latest
If any of the prior messages were significant, I can't imagine podman 
bothering to try and pull the image.  If the prior messages are 
harmless, it suggests troubleshooting should start with:
systemd[746]: cms_backend.service: Main process exited, code=exited, 
status=125/n/a
Looking at your quadlet files, I noticed:
Exec=/bin/bash -c "pip install -q -e . \
...cut...
but cannot see a closing " (quote) anywhere in that big Exec string. 
Hopefully this is copy-paste error.  I can't imagine how it could work 
manually with a missing quote like that.
Chris Evich (he/him), RHCA III
Senior Quality Assurance Engineer
If it ain't broke, your hammer isn't wide 'nough.
On 5/29/23 03:32, jklaiho(a)iki.fi wrote:
 The IP firewall warning seems to be unrelated. On another server
where 
 we didn't get this problem on a reboot, the same warning is emitted for 
 one of the several rootless containers running there. It's interesting 
 on its own, and I found where it happens in the systemd code here:
 
https://github.com/systemd/systemd/blob/e30b4c13570a5e4ec794d480d5371e9c7...
<
https://github.com/systemd/systemd/blob/e30b4c13570a5e4ec794d480d5371e9c7...
 
 ...but that seems like another, likely benign issue with rootless Podman 
 and systemd/cgroups, maybe?
 
 The later errors seem to be the actual failure here, but I don't know 
 what to make of them.
 
 
 - JK
 
 
 
 
     On Thursday, May 25, 2023 at 7:21 PM, Chris Evich <cevich(a)redhat.com
     <mailto:cevich@redhat.com>> wrote:
     On 5/25/23 08:03, jklaiho(a)iki.fi wrote:
>     systemd[746]: cms_backend.service: unit configures an IP firewall,
>     but not running as root.
>     systemd[746]: (This warning is only shown for the first unit using
>     IP firewalling.)
 
     I'm not an expert, but to my untrained eye, this message seems to be
     the
     root-cause indicator. I can't say for sure where/why that error is
     generated but it seems like it could be some kind of bug in quadlet
     interactions w/ the rest of systemd. Maybe try changing the
     dependencies (Wants/After) might make a difference? That's a total
     guess though.
 
     ---
     Chris Evich (he/him), RHCA III
     Senior Quality Assurance Engineer
     If it ain't broke, your hammer isn't wide 'nough.
     _______________________________________________
     Podman mailing list -- podman(a)lists.podman.io
     To unsubscribe send an email to podman-leave(a)lists.podman.io