Docker container fails to start due to missing gunicorn parameter

[coffeemakingtoaster]

A clear and concise description of what the bug is.

How to reproduce the bug

1. Run the latest tag of the superset docker image as described on the dockerhub page. docker run -d -p 8080:8088 --name superset apache/superset

Expected results

The container should start normally.

Actual results

The container terminates due to the following error

usage: gunicorn [OPTIONS] [APP_MODULE]
gunicorn: error: argument --max-requests: expected one argument

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.

Additional context

In my case the issue occurs on a linux/arm64 system. I currently cannot test if this issue is exclusive to linux/arm64 systems.

[coffeemakingtoaster]

Closing this due to it already being mentioned and fixed on the PR that introduced the issue in the first place.
#20733