joeyorlando
commented
1 week ago This issue does not occur in Docker, where the Celery container restarts as expected
Closing as this appears to be specific to podman (we don't provide support for specific setup cases like this)
What went wrong?
What happened: -In a Podman environment using podman-compose, the Celery worker is set to shut down every 5 minutes as specified by the environment variable CELERY_WORKER_SHUTDOWN_INTERVAL="5m". However, after the specified interval and a successful shutdown, Celery fails to restart, despite restart: always being set in the podman-compose.yml file. This issue does not occur in Docker, where the Celery container restarts as expected.
What did you expect to happen: -Celery should automatically restart in Podman after it shuts down due to the CELERY_WORKER_SHUTDOWN_INTERVAL interval. With restart: always set, Podman should initiate a restart immediately after the Celery container stops.
How do we reproduce it?
use podman-compose to run the default docker-compose.yml
Grafana OnCall Version
1.12.1
Product Area
Helm/Kubernetes/Docker
Grafana OnCall Platform?
None
User's Browser?
No response
Anything else to add?
No response