question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Empty screen after docker-compose build & up

See original GitHub issue

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

Expected results

Get a working Superset.

Actual results

Empty screen.

Screenshots

Screenshot 2020-02-11 at 14 37 44

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/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 Analytics

  • State:closed
  • Created 4 years ago
  • Reactions:19
  • Comments:16 (2 by maintainers)

github_iconTop GitHub Comments

6reactions
mona-mkcommented, Jan 6, 2021

Solution is to wait until it gets fully complied (~ 10min on macOS Catalina 2,6 GHz 6-Core Intel Core i7)

3reactions
damnkocommented, Dec 27, 2020

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

Read more comments on GitHub >

github_iconTop Results From Across the Web

Empty screen after docker-compose build & up #9116 - GitHub
I faced the same problem (empty screen) when building and installing from the current master. It turns out that I missed some major...
Read more >
Got a blank page after running docker-compose up. - Setup
I run docker-compose up -d on my mac mini. When I browse to http://localhost I got a blank page as shown in the...
Read more >
Docker-compose produces Docker Desktop whiteout
Just a white screen is shown. When I close the app and restart it, I see the app's desktop flashing for a millisecond,...
Read more >
Docker compose build | Image after pull does not work / is empty
Docker will create the image successfully. I push it to HUB via Docker Desktop and my colleague can pull it. But the pulled...
Read more >
Blank Page Syndrome : Can Docker Really Help Me? Up ...
My first question when I hear of a new tool is “Will it really ... Let's create a docker-compose.yml file from the CouchDb...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found