Install results in broken welcome screen on MacOS

[HappyMiner]

A clear and concise description of what the bug is.

Expected results

Following the steps on:
https://superset.apache.org/docs/installation/installing-superset-using-docker-compose

I expect to be able to use superset after doing "docker-compose up" and logging in.

Actual results

I am able to login but only see a broken screen, displaying 3 items:

• "x" button
• "close" button
• broken image picture

Screenshots

Please see attached screenshot.

How to reproduce the bug

Follow instructions to install and run on MacOS as described in:
https://superset.apache.org/docs/installation/installing-superset-using-docker-compose

Login and find the broken page.

Environment

(please complete the following information):

• superset version: unknown
  There is no version information anywhere to be found. I did "git clone https://github.com/apache/incubator-superset.git" on TUE OCT 6th at around 08:27 New York time if that helps.

• python version: python --version:
  Python 2.7.16 but Python 3.7.6 is also installed

• node.js version: node -v:
  I do not have node installed.

• npm version: npm -v
  No NPM on Mac.

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.
  WHERE to find these?

• I have reproduced the issue with at least the latest released version of superset.
  I tried to do docker-compose build AND docker-compose up --build to see if this could fix the issue. No change.

• I have checked the issue tracker for the same issue and I haven't found one similar.
  I have found one issue from 2019: Superset dashboard or no data loading after login #8818
  But nothing in there seemed to help me.

Additional context

While I was typing this I saw the terminal showing additional information:

"superset_node | npm WARN tarball tarball data for datamaps@0.5.9 (sha512-GUXpO713URNzaExVUgBtqA5fr2UuxUG/fVitI04zEFHVL2FHSjd672alHq8E16oQqRNzF0m1bmx8WlTnDrGSqQ==) seems to be corrupted. Trying one more time."

I then scrolled up to check if there was more and got to:

"superset_init | Init Step 4/4 [Starting] -- Loading examples"

I did not find the related "[Complete]" tag however. Does this mean that there is still some kind of installation running in the background? If this is the case and the install is still running, why not tell the user clearly? Also why can I already open the URL if there is nothing there (yet)? Most likely something went wrong during the install and Step 4 never got completed I guess?

The terminal gets flooded with "superset_app | INFO:werkzeug:127.0.0.1 - - [06/Oct/2020 12:34:25] "GET /health HTTP/1.1" 200 -" which to me looks like an "is_alive" response, telling me, as the unsuspecting user, that everything is done.

[issue-label-bot]

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

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

[HappyMiner]

Just after I hit submit here, it seems that the terminal came alive again:
Seeing messages about a "webpack.Progress"... If the installation is not completed after... well, completing it, then the user should definitely be warned at least in the documentation. For me this whole thing has been going on for about at least an hour, I think, including one rebuild attempt because of this.

[srinify]

@HappyMiner hi there, this has actually been a common experience for many first time users of Superset via docker-compose. The Docker container for the frontend application is basically building frontend assets (hence the webpack.progress messages in the command line) but this build process often starts 10-15 mins after the rest of the containers are up (for some reason).

Once you see the frontend assets finish building, you should see the full Superset UI!

[mattarderne]

I encountered this and waiting for +20min without it resolving. What am I looking for to indicate it is finished building?

[nytai]

@mattarderne You're looking for the superset_node container to finish building the front end assets.

[mattarderne]

Per this comment, working steps for me are as follows:

docker-compose build
docker-compose up

I also increased the ec2 instance size to medium, perhaps this helped.

[Bloomberg-zhong]

same question, what should I do to fix it?

[gamebusterz]

@Bloomberg-zhong
Running docker-compose down before running the below commands worked for me.

docker-compose build
docker-compose up

[fulviomascara]

I solved this problem in my Mac today, with these steps:

1. git clone https://github.com/apache/incubator-superset.git
2. cd incubator-superset
3. docker-compose build
4. docker-compose up

After terminal finishes Load Examples step (Step 4), enter in another session in terminal and
5. npm ci && npm run build && rm -rf node_modules

[bharathi26]

I solved this problem in my Mac today, with these steps:

1. git clone https://github.com/apache/incubator-superset.git
2. cd incubator-superset
3. docker-compose build
4. docker-compose up

After terminal finishes Load Examples step (Step 4), enter in another session in terminal and
5. npm ci && npm run build && rm -rf node_modules

Thanks a lot

[JoseCF]

I solved this problem in my Mac today, with these steps:

1. git clone https://github.com/apache/incubator-superset.git
2. cd incubator-superset
3. docker-compose build
4. docker-compose up

After terminal finishes Load Examples step (Step 4), enter in another session in terminal and
5. npm ci && npm run build && rm -rf node_modules

Could you tell us in which image do you open the terminal: superset-worker, superset-app????

[gamebusterz]

Could you tell us in which image do you open the terminal: superset-worker, superset-app????

It clearly says you have to be in incubator-superset, which is just the root directory of the project

[tomer-ben-david]

npm ci && npm run build && rm -rf node_modules

I get then:

npm ci && npm run build && rm -rf node_modules                                                                               (base)
npm ERR! The `npm ci` command can only install with an existing package-lock.json or
npm ERR! npm-shrinkwrap.json with lockfileVersion >= 1. Run an install with npm@5 or
npm ERR! later to generate a package-lock.json file, then try again.

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/..../.npm/_logs/2021-01-26T15_34_29_045Z-debug.log

[bobeal]

npm ci && npm run build && rm -rf node_modules

I get then:

npm ci && npm run build && rm -rf node_modules                                                                               (base)
npm ERR! The `npm ci` command can only install with an existing package-lock.json or
npm ERR! npm-shrinkwrap.json with lockfileVersion >= 1. Run an install with npm@5 or
npm ERR! later to generate a package-lock.json file, then try again.

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/..../.npm/_logs/2021-01-26T15_34_29_045Z-debug.log

you have to first go into the superset-frontend directory (where the build files for the front end are located) and run the npm ... commands in it.