superset: docker-compose up, reaches completion of init Step 4, but the welcome screen is not functional

A clear and concise description of what the bug is.

Expected results

A functional welcome screen after successful login (admin, admin)

Actual results

The welcome screen (http://localhost:8088/superset/welcome ) contains three items, two (non functional) buttons (one shows x, other shows close) and a not-loaded image (maybe loading.gif). Otherwise the welcome page is blank. During docker-compose up I noticed some lines in red which may be errors. See attachment for the stdout of the docker-compose up.

Screenshots

N/A

How to reproduce the bug

Using ubuntu 18.04.5 LTS with docker 19.03.12 with docker-compose 1.26.2

On 03/September/2020

git clone https://github.com/apache/incubator-superset/ cd incubator-superset docker-compose up

…when stdout showed Init Step 4/4 [Complete] -- Setting up roles and perms

opened my browser (either chromium or firefox latest) at http://localhost:8088 Login admin with password admin (success) The browser displays the url localhost:8088/superset/welcome, but that seems to be a mostly empty screen , with two buttons, one with x, other with Close. Clicking on either of these buttons has no effect.

There is also an image in the centre of the screen , maybe loading.fig, but not rendered.

Environment

  • superset version: superset version $ git log commit 824cea24bad8aa330f288142cab989407577e3af (HEAD -> master, origin/master, origin/HEAD) Author: Evan Rusackas evan@preset.io Date: Wed Sep 2 23:13:58 2020 -0700

    More Label touchups (margins) (#10722)

    • labels with onClick don’t need .pointer. No labels need m-r-5

    • making Timer a proper Label

    • a little linting

    • addresing (helpful, thanks) comment

  • python version: python --version (per dockerfile)

  • node.js version: node -v (per dockerfile)

  • npm version: npm -v (per dockerfile)

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

N/A

About this issue

  • Original URL
  • State: closed
  • Created 4 years ago
  • Reactions: 1
  • Comments: 18 (4 by maintainers)

Most upvoted comments

@dpgaspar I ran: docker-compose down docker-compose build docker-compose up

When it had completed, I opened the browser to http://localhost:8088 and this time, the welcome screen appears to be functional.

So it seems that in my case the docker-compose build is a necessary step, but somehow this is not mentioned at the instructions page currently. This is a gotcha. Would be useful if the documentation page at https://superset.incubator.apache.org/installation.html could be updated to give newbies a clue.

I’m testing it now… and waiting 30+ min…

Result is the same(white-screen with 2 buttons), and the resources are not found. http://localhost:8088/static/assets/images/loading.gif http://localhost:8088/static/assets/images/superset-logo-horiz.png

Not Found The requested URL was not found on the server. If you entered the URL manually please check your spelling and try again.

How to check which process is running in background?

$ docker logs superset_node -f npm WARN using --force I sure hope you know what you are doing. /usr/local/bin/webpack-cli -> /usr/local/lib/node_modules/webpack-cli/bin/cli.js /usr/local/bin/webpack -> /usr/local/lib/node_modules/webpack/bin/webpack.js

  • webpack-cli@4.5.0
  • webpack@5.21.2 added 126 packages from 161 contributors in 36.031s npm WARN using --force I sure hope you know what you are doing.

Wow, it sure does take a long time. It took nearly an hour just to install all the packages on my machine:

superset_node            | added 5715 packages from 2250 contributors and audited 5765 packages in 3187.699s

Then the webpack build itself was another ~30mins.

Similar experience: image

This is what I got after clone the repo and follow the instructions described here: https://superset.incubator.apache.org/installation.html

superset_app             | 172.21.0.1 - - [19/Nov/2020 18:01:19] "GET /static/assets/images/loading.gif HTTP/1.1" 404 -
superset_app             | INFO:werkzeug:172.21.0.1 - - [19/Nov/2020 18:01:19] "GET /static/assets/images/loading.gif HTTP/1.1" 404 -

Seems getting 404 for these static assets

Solved: You just need to wait, webpack takes some time to build your assets. Just leave in background and wait for magic.