superset: Apache Superset is not starting line 50: /usr/bin/run-server.sh: No such file or directory

Apache Superset docker-compose is not working for a newly cloned project and by following the offical documentation: https://superset.apache.org/docs/installation/installing-superset-using-docker-compose

How to reproduce the bug

Clone the superset git locally
Run docker-compose -f docker-compose-non-dev.yml up

Expected results

The application should start.

Actual results

The web application is not starting and the log shows the following error:

superset_app            | Starting web app...
superset_app            | /app/docker/docker-bootstrap.sh: line 50: /usr/bin/run-server.sh: No such file or directory

Screenshots

If applicable, add screenshots to help explain your problem.

Environment

git checkout today 10.12.2021, no changes on my side just the latest repository

About this issue

Original URL
State: closed
Created 3 years ago
Reactions: 7
Comments: 23 (11 by maintainers)

Commits related to this issue

docs(docker compose installation) : add pull command to avoid errors when installing superset using docker compose. fixes #17712 — committed to ancasarb/superset by deleted user 2 years ago
docs(docker compose installation) : add pull command to avoid errors when installing superset using docker compose. fixes #17712 (#18196) Co-authored-by: asarb <asarb@expediagroup.com> — committed to apache/superset by ancasarb 2 years ago
docs(docker compose installation) : add pull command to avoid errors when installing superset using docker compose. fixes #17712 (#18196) Co-authored-by: asarb <asarb@expediagroup.com> — committed to casual-precision/superset by ancasarb 2 years ago
docs(docker compose installation) : add pull command to avoid errors when installing superset using docker compose. fixes #17712 (#18196) Co-authored-by: asarb <asarb@expediagroup.com> — committed to nielsen-oss/superset by ancasarb 2 years ago
docs(docker compose installation) : add pull command to avoid errors when installing superset using docker compose. fixes #17712 (#18196) Co-authored-by: asarb <asarb@expediagroup.com> — committed to casual-precision/superset by ancasarb 2 years ago

Most upvoted comments

@caleb15 this issue should be resolved in the upcoming 1.5.0 release.

eschutho on Apr 1, 2022

1.4.1 still has the same issue for me

gai6948 on Feb 16, 2022

Running docker-compose -f docker-compose-non-dev.yml pull before running the up command should fix this. The issue is that the version of code you are on is not compatible with the docker image you have, so you need to pull a newer docker image that is compatible with this code

nytai on Jan 26, 2022

@wiktor2200 I have found this discussion for 1.4.0 bugs that are candidates for being fixed in 1.4.1 -> https://github.com/apache/superset/discussions/18119

rafalpas on Jan 25, 2022

Same issue for me with 0.5.8 chart and 1.4.1 image. It’s ok with 0.4.0 chart

arkpoah on Feb 22, 2022

The problem exists in 1.4.0. There shouldn’t be so many differences and long periods of time between releases, because there are a lot of changes everywhere and there is no way to use default helm chart values with stable version. 😦 Yesterday release is based on commit from OCTOBER 2021 which causes 3,5months of fixes and improvements missing in new release. There is 285 changed files with 8,931 additions and 22,463 deletions difference between current master and release tag 1.4.0 @eschutho is there any roadmap for release 1.4.1 or any timetable when next release will cover those changes.

It would be good to add some tests for helm chart deployment for both latest and stable version.

@wiktor2200 1.4.1 will only include bug fixes (not features) that address issues on 1.4.0, so of those 285 changes, only a small portion will apply. 1.4.1 is scheduled to go for vote in the next few days. Please mention any bug fixes that need to be added to the release here: https://github.com/apache/superset/discussions/18119

eschutho on Jan 26, 2022