Error when using docker-compose up: "ModuleNotFoundError: No module named 'superset.app'"

[devlace]

When attempting to run "docker-compose up", I'm getting an error in superset_1 "ModuleNotFoundError: No module named 'superset.app'". When navigating to localhost:8088. I get the error "flask.cli.NoAppException: Could not import "superset.app"'

Expected results

After running docker-compose up, I expect a functioning app at localhost:8088

Actual results

Error when navigating to localhost:8088

Screenshots

If applicable, add screenshots to help explain your problem.

How to reproduce the bug

1. Clone repo, and checkout tag 0.36.0 (latest release as of 2020/06/30).
2. cd in to incubator-superset
3. Run docker-compose up

Environment

• superset version: 0.36.0
• docker engine version: 19.03.8
• docker compose version: 1.26.0

Checklist

Make sure these boxes are checked 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

Add any other context about the problem here.

[issue-label-bot]

Issue-Label Bot is automatically applying the label #bug to this issue, with a confidence of 0.67. Please mark this comment with 👍 or 👎 to give our bot feedback!

Links: app homepage, dashboard and code for this bot.

[willbarrett]

Please attempt rebuilding from scratch as described here: #10149 (comment)

Please re-open if that does not resolve your issue.

[petsasj]

I have the exact same issue.

Tried the nuke method in the linked comment, however nothing changed.

I also tried to check out different branches - as in previous versions to no avail.

Here's the system info:
OS: centos 7.7
Superset version: 0.37.2 (latest) [also tested 0.36]
Docker version: 1.13.1
Docker-compose version: 1.27.4

I figured it was a better option to comment on this issue rather than opening a new one.

I can provide further Log files if needed