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.

UI not working in docker production setup.

See original GitHub issue

Expected results

what you expected to happen. After login with admin/admin for production docker running image, there is no menu/dashboard showing up.

Actual results

what actually happens.

Instead it shows up some blank page with a button.

Screenshots

2020-01-15_12-45-48

How to reproduce the bug

changes in .env file as production for FLASK_ENV and SUPERSET_ENV.
run sudo SUPERSET_LOAD_EXAMPLES=yes docker-compose run --rm superset ./docker-init.sh
run sudo docker-compose up
go to the endpoint login page in the browser. Enter admin/admin. You can see a blank page with a button in it and nothing else.

Environment

Latest from master branch

superset version: superset version
python version: python --version
node.js version: node -v
npm version: npm -v

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

Log attached below.

Log

Issue Analytics

State:
Created 4 years ago
Reactions:6
Comments:9

Top GitHub Comments

2reactions

DylanNWattcommented, Jan 19, 2020

I also came across this, and after a long debugging session I walked away, came back, and it was working. I’m pretty sure it’s just that you’re able to access the webpage long before the npm installation process has completed. If you inspect the source of the returned page when it’s in that state, there are no script tags embedded.

After waiting for about 15 minutes on a modern macbook pro, the logs progressed from npm ci step to the actual build, and it started working. The fix here is probably just not starting the web server until the build is complete, and adding more clear logging after npm ci of “Installing web dependencies, this may take a while.”

2reactions

issue-label-bot[bot]commented, Jan 15, 2020

Issue-Label Bot is automatically applying the label #bug to this issue, with a confidence of 0.86. Please mark this comment with 👍 or 👎 to give our bot feedback!

Links: app homepage, dashboard and code for this bot.