I am using an Azure DevOps self hosted agent to automate starting containers on an Azure VM. The agent uses the "podman-compose up -d" command and all is well as long as the agent's job is still executing. When all containers in the compose file are started the job ends and some containers fail with the following error:
I have failed to find any more details about the error by attaching the volume to the container's logs folder. The problem does not occur when the agent uses the "podman-compose up" command (without detached) which obviously makes it run indefinately. The problem also doesn't happen when I run "podman-compose" myself. I am running the containers rootless, using podman version 5.2.2, podman-compose version 1.3.0, the VM is running RHEL 9.5 and the agent's version is 4.248.0 and is running as an systemd service. I have also enabled lingering for the user running the agent. I find it puzzling that both podman and cockpit report the container as "running" even though it visibly is not. Does anyone know what might be causing it? I appreciate all help :)
