srinify edited a comment on issue #12851: URL: https://github.com/apache/superset/issues/12851#issuecomment-770429813
Hey there! This is actually a common experience if you use Superset through Docker Compose. Essentially the frontend assets are still building. After you do `docker-compose up`, if you could wait 15-30 minutes (this is really only needed the first time) then the frontend should be ready (to confirm, try opening the local URL in an incognito browser and logging). If you're running docker-compose with the logs pouring out in your command line, you'll see 1% -> 100% logs being dumped. It will look kinda like: <img width="1443" alt="Screen Shot 2021-01-31 at 1 47 44 PM" src="https://user-images.githubusercontent.com/801507/106394510-f337dc00-63ca-11eb-8b47-3addc7250488.png"> You can also restart the `superset_node` container from the Docker UI: - Open the Docker app on your operating system (it might be in your system tray) - Click on Dashboard - Expand `superset` and then click the Restart button for `superset_node`. - Wait 20-30 minutes and your frontend should work Also -- make sure you have at least 8 GB allocated to Docker. You can also edit this / increase in the Docker GUI / app ^ This will likely be documented this week! ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
