[docker-compose] Problems with Celery beat when the machine is rebooted suddenly

[alvarolmedo]

A clear and concise description of what the bug is.

How to reproduce the bug

1. Run apache superset using docker compose:

docker compose -f docker-compose-non-dev.yml up

2. With containers running, reboot the machine.

Expected results

All the containers start and running correctly again.

Actual results

The superset_worker_beat container enter in restarting state. The logs shows:

Loaded your LOCAL configuration at [/app/docker/pythonpath_dev/superset_config.py]
celery beat v5.2.2 (dawn-chorus) is starting.
ERROR: Pidfile (/tmp/celerybeat.pid) already exists.
Seems we're already running? (pid: 10)

Environment

• superset version: 2.1.0

Checklist

Make sure to follow these steps before submitting your issue - thank you!

• I have checked the superset logs for python stacktraces and included it here as text if there are any.
• I have reproduced the issue with at least the latest released version of superset.
• I have checked the issue tracker for the same issue and I haven't found one similar.