Issue 1:
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

docker-compose build

docker-compose up

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/superset-logo@2x.png HTTP/1.1" 404 -
superset_1 | INFO:werkzeug:172.18.0.1 - - [11/Feb/2020 13:37:23] "GET /static/assets/images/superset-logo@2x.png HTTP/1.1" 404 -
superset_1 | 172.18.0.1 - - [11/Feb/2020 13:37:23] "GET /static/assets/images/superset-logo@2x.png HTTP/1.1" 404 -
superset_1 | INFO:werkzeug:172.18.0.1 - - [11/Feb/2020 13:37:23] "GET /static/assets/images/superset-logo@2x.png 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 -

Issue 2:
I am using the docker image to use Apache superset, I followed the instructions.

I cloned the git repository then a docker-compose up

Expected results

The UI to load

Actual results

The UI won't load, here is a screenshot

How to reproduce the bug

I followed the instructions to use the docker image.

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

the docker logs show that incubator-superset_superset-node_1 fails to cd into /app/superset-frontend/, I am getting the following error message:

superset-node_1 | bash: line 0: cd: /app/superset-frontend/: No such file or directory

The problematic instruction lies in the docker-compose.yml file; line 69:

command: ["bash", "-c", "ls /app/ && cd /app/superset-frontend/ && npm install && npm run dev"]