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.

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

See original GitHub issue

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

Issue Analytics

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

github_iconTop GitHub Comments

3reactions
imavocommented, Sep 8, 2020

@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.

2reactions
javidschcommented, Feb 12, 2021

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.
Read more comments on GitHub >

github_iconTop Results From Across the Web

[GitHub] [incubator-superset] imavo commented ... - The Mail Archive
... [incubator-superset] imavo commented on issue #10773: docker-compose up, reaches completion of init Step 4, but the welcome screen is not functional.
Read more >
docker compose up - Docker Documentation
When the command exits, all containers are stopped. Running docker compose up --detach starts the containers in the background and leaves them running....
Read more >
Try Docker Compose - Docker Documentation
Step 4 : Build and run your app with Compose​​ From your project directory, start up your application by running docker compose up...
Read more >
Frequently asked questions - Docker Documentation
The docker compose start command is useful only to restart containers that were previously created, but were stopped. It never creates new containers....
Read more >
How to Fix and Debug Docker Containers Like a Superhero
And while it's not always obvious how container errors occur, this mystery is even harder for newer developers to unravel.
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