Incubator-superset: Empty screen after docker-compose build & up

[l1x]

Superset is not starting up properly after docker-compose build & up

Expected results

Get a working Superset.

Actual results

Empty screen.

Screenshots

How to reproduce the bug

1. docker-compose build
2. docker-compose up
3. See error

Environment

• superset version: latest in from source
• python version: Python 3.6.9

Checklist

Make sure these boxes are checked before submitting your issue - thank you!

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

Additional context

superset_1         | INFO:werkzeug:172.18.0.1 - - [11/Feb/2020 13:37:23] "GET /logout/ HTTP/1.1" 302 -
superset_1         | 172.18.0.1 - - [11/Feb/2020 13:37:23] "GET / HTTP/1.1" 302 -
superset_1         | INFO:werkzeug:172.18.0.1 - - [11/Feb/2020 13:37:23] "GET / HTTP/1.1" 302 -
superset_1         | 172.18.0.1 - - [11/Feb/2020 13:37:23] "GET /superset/welcome HTTP/1.1" 302 -
superset_1         | INFO:werkzeug:172.18.0.1 - - [11/Feb/2020 13:37:23] "GET /superset/welcome HTTP/1.1" 302 -
superset_1         | 172.18.0.1 - - [11/Feb/2020 13:37:23] "GET /login/ HTTP/1.1" 200 -
superset_1         | INFO:werkzeug:172.18.0.1 - - [11/Feb/2020 13:37:23] "GET /login/ HTTP/1.1" 200 -
superset_1         | 172.18.0.1 - - [11/Feb/2020 13:37:23] "GET /static/assets/images/[email protected] HTTP/1.1" 404 -
superset_1         | INFO:werkzeug:172.18.0.1 - - [11/Feb/2020 13:37:23] "GET /static/assets/images/[email protected] HTTP/1.1" 404 -
superset_1         | 172.18.0.1 - - [11/Feb/2020 13:37:23] "GET /static/assets/images/[email protected] HTTP/1.1" 404 -
superset_1         | INFO:werkzeug:172.18.0.1 - - [11/Feb/2020 13:37:23] "GET /static/assets/images/[email protected] HTTP/1.1" 404 -
superset_1         | 172.18.0.1 - - [11/Feb/2020 13:37:27] "POST /login/ HTTP/1.1" 302 -
superset_1         | INFO:werkzeug:172.18.0.1 - - [11/Feb/2020 13:37:27] "POST /login/ HTTP/1.1" 302 -
superset_1         | 172.18.0.1 - - [11/Feb/2020 13:37:27] "GET / HTTP/1.1" 302 -
superset_1         | INFO:werkzeug:172.18.0.1 - - [11/Feb/2020 13:37:27] "GET / HTTP/1.1" 302 -
superset_1         | 172.18.0.1 - - [11/Feb/2020 13:37:27] "GET /superset/welcome HTTP/1.1" 200 -
superset_1         | INFO:werkzeug:172.18.0.1 - - [11/Feb/2020 13:37:27] "GET /superset/welcome HTTP/1.1" 200 -
superset_1         | 172.18.0.1 - - [11/Feb/2020 13:37:27] "GET /static/assets/images/loading.gif HTTP/1.1" 404 -
superset_1         | INFO:werkzeug:172.18.0.1 - - [11/Feb/2020 13:37:27] "GET /static/assets/images/loading.gif HTTP/1.1" 404 -
superset_1         | 127.0.0.1 - - [11/Feb/2020 13:37:36] "GET /health HTTP/1.1" 200 -
superset_1         | INFO:werkzeug:127.0.0.1 - - [11/Feb/2020 13:37:36] "GET /health HTTP/1.1" 200 -
superset_1         | 127.0.0.1 - - [11/Feb/2020 13:38:06] "GET /health HTTP/1.1" 200 -
superset_1         | INFO:werkzeug:127.0.0.1 - - [11/Feb/2020 13:38:06] "GET /health HTTP/1.1" 200 -

[hozn]

Seeing same issue here on a clean install (MacOS -- with updated resource limits so that build would work).

This may be unrelated, but it would appear that incubator-superset_superset-node_1 has stopped with exit 1:

$ docker logs incubator-superset_superset-node_1
bash: line 0: cd: /app/superset-frontend: No such file or directory
bash: line 0: cd: /app/superset-frontend: No such file or directory

(Indeed, there's no superset-frontend that would be expected in the configured service, which simply uses a debian jesse base image with no mapped-in /app/superset-frontend directory.)

[vikt0rs]

Seems to be duplicate of https://github.com/apache/incubator-superset/issues/9108

[nytai]

should be fixed by: https://github.com/apache/incubator-superset/pull/9114

[willbarrett]

Hi @l1x and @vikt0rs - are you still experiencing this issue?

[l1x]

Hi @l1x and @vikt0rs - are you still experiencing this issue?

It worked after the update.

[vikt0rs]

works for me as well, thanks!

[inetfuture]

I had the same symptom, the cause is the npm install command of superset-node container did not run successfully due to network failure(I'm at China mainland), I had to mannuly set the npm registry to a China mirror to make it work, posting here just in case someone else run into this.

[Meizuamy]

I had the same symptom, the cause is the npm install command of superset-node container did not run successfully due to network failure(I'm at China mainland), I had to mannuly set the npm registry to a China mirror to make it work, posting here just in case someone else run into this.

I hava the same problem when i install the superset ,can u tell me how can i change the npm registry.

[damnko]

I'm also having this issue with a clean install on mac, following the instructions here https://superset.apache.org/docs/installation/installing-superset-using-docker-compose. Any hints on how to solve it? Thanks