Hi,
I have a quadlet that I inject into an Azure VM CoreOs using ignition. Fedora CoreOS v1.5.0 | Butane
quadlet email-sifting:
[Unit]
Description=CCS Email Sifting
Requires=acrlogin.service
After=acrlogin.service
[Container]
Image=host.azurecr.io/email-sifting:latest
EnvironmentHost=true
[Install]
WantedBy=multi-user.target
This worked great last week. Now this week, and not sure if its when I upgraded to 41, it blows up with the following errors:
Dec 19 14:57:40 email-sifting-uat1 systemd[1]: Starting email-sifting.service - CCS Email Sifting...
Dec 19 14:57:40 email-sifting-uat1 podman[1470]: 2024-12-19 14:57:40.786642371 +0000 UTC m=+0.080832249 image pull f212fbf7724a0cb79dd8c88d41a7ebc768fe8373584148ac9ad5284558c4a1b0 host.azurecr.io/email-sifting:latest
Dec 19 14:57:40 email-sifting-uat1 podman[1470]: 2024-12-19 14:57:40.916580093 +0000 UTC m=+0.210769871 container create d575e73771a634b9c6b45e9b51919f7c3d2ffba1f32a1f3a95d05cbf356f2ee9 (image=host.azurecr.io/email-sifting:latest, name=systemd-email-sifting, PODMAN_SYSTEMD_UNIT=email-sifting.service, io.buildah.version=1.38.0)
Dec 19 14:57:41 email-sifting-uat1 conmon[1696]: conmon d575e73771a634b9c6b4 <nwarn>: runtime stderr: executable file `bash` not found in $PATH: No such file or directory
Dec 19 14:57:41 email-sifting-uat1 conmon[1696]: conmon d575e73771a634b9c6b4 <error>: Failed to create container: exit status 1
Dec 19 14:57:42 email-sifting-uat1 podman[1470]: 2024-12-19 14:57:42.069531206 +0000 UTC m=+1.363721084 container remove d575e73771a634b9c6b45e9b51919f7c3d2ffba1f32a1f3a95d05cbf356f2ee9 (image=host.azurecr.io/email-sifting:latest, name=systemd-email-sifting, PODMAN_SYSTEMD_UNIT=email-sifting.service, io.buildah.version=1.38.0)
Dec 19 14:57:42 email-sifting-uat1 email-sifting[1470]: Error: crun: executable file `bash` not found in $PATH: No such file or directory: OCI runtime attempted to invoke a command that was not found
Dec 19 14:57:42 email-sifting-uat1 systemd[1]: email-sifting.service: Main process exited, code=exited, status=127/n/a
Dec 19 14:57:42 email-sifting-uat1 systemd[1]: email-sifting.service: Killing process 1696 (conmon) with signal SIGKILL.
Dec 19 14:57:42 email-sifting-uat1 systemd[1]: email-sifting.service: Killing process 1700 (podman) with signal SIGKILL.
Dec 19 14:57:42 email-sifting-uat1 systemd[1]: email-sifting.service: Killing process 1702 (podman) with signal SIGKILL.
Dec 19 14:57:42 email-sifting-uat1 systemd[1]: email-sifting.service: Killing process 1704 (podman) with signal SIGKILL.
Dec 19 14:57:42 email-sifting-uat1 systemd[1]: email-sifting.service: Killing process 1725 (podman) with signal SIGKILL.
Dec 19 14:57:42 email-sifting-uat1 systemd[1]: email-sifting.service: Killing process 1726 (n/a) with signal SIGKILL.
Dec 19 14:57:42 email-sifting-uat1 systemd[1]: email-sifting.service: Killing process 1729 (n/a) with signal SIGKILL.
Dec 19 14:57:42 email-sifting-uat1 systemd[1]: email-sifting.service: Failed with result 'exit-code'.
Dec 19 14:57:42 email-sifting-uat1 systemd[1]: Failed to start email-sifting.service - CCS Email Sifting.
However if I login and run:
sudo podman run --env-host host.azurecr.io/email-sifting:latest
it runs absolutely fine, like it did before.
Any idea what could be causing this failure now, or how I can narrow it down.