Installing Superset via Docker-compose Up #9880
Comments
|
Solution: Isntalling |
|
@smirs Hi, sorry how did you install node and vpm?..I'm having the same problem, I notice that there are several containers
in my case I'm getting several logs indicating an issue with some npm dependencies
|
|
Facing same issue with docker-compose up |
|
@craig-rueda , who has most context on our docker / docker-compose |
|
Could be related to the node modules volume? Try re-pulling master and re-up. |
|
same problem +1 |
|
Try leaving it to run for about 5 - 10 minutes. I had the same issue but leaving it webpack started printing messages and eventually I was able to load it when webpack finished but took about 5 minutes locally |
|
Thanks for reaching out, guys. We're aware of this lagginess when it comes
to the node container and are actively looking at it. Thanks again, and
stay tuned for updates!
…-Craig
On Thu, Jul 16, 2020 at 8:03 AM Robert Brown ***@***.***> wrote:
Try leaving it to run for about 5 - 10 minutes. I had the same issue but
leaving it webpack started printing messages and eventually I was able to
load it when webpack finished but took about 5 minutes locally
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#9880 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AATZTWYWTHUEZJRPHMEVG5DR34JD7ANCNFSM4NHHRZUA>
.
|
|
I'm having this issue as well. This is my log. I also nuked the volumes, reran compose up, and pulled the lastest from master. EDIT: Also got this issue when I followed this |
|
Same here!. The problem was the amount of memory allocated to Docker. I increased ram and cpu and solved. |
|
I have experienced similar issue when trying to setup superset for the first time. Hopefully this could be resolved so we can lower the barrier for people who is excited about superset's potential |
|
I also experienced the same issue when trying to deploy on my MacBook Pro. Tried a few things, no luck yet. Will keep trying. Any suggetions? |
|
same on fresh install ubuntu 18.04 LTS vm. install via github. |
|
@thanwin - looks to me like you need to bump your Docker memory limits in order to allow for the |
I am facing the same issue, may I ask how did you solve the problem? |
|
same problem +1 again |
|
same problem |
|
I solved it by:
|
|
Worked for me now after reinstalling Docker, increasing Docker memory to 16GB, running "docker-compose up" and waiting for about 15 minutes after superset-frontend node_module build complete. Thanks for sharing the tips @guys. The authentication is ready earlier in the process, the frontend along with all the super rich data/dashboard taking time to process, maybe a placeholder message in UI and server log will help |
|
Thanks for the updates. I will bump up docker to 16GB and wait. |
|
Wait around 5 minutes until it stop printing on the screen, then you're all set. But it may use large amount of ram so you might increase docker ram to 16GB like others said. |
|
Facing similar issue on Ubuntu 20.04 LTS via WSL 2 on Docker for Windows with WSL 2 Integration |
and.... fixed itself after a few hours.. of idling |
|
We've noticed in the past that building the javascript bundles is pretty io intensive and that docker in some context doesn't do io as well. OSx used to be pretty bad and things could degrade while in container-in-container mode. Unclear how Docker on Windows does with this. Unclear if that's the part of the issue or not, but something to keep in mind. |
|
I experienced the same kind of behaviour, restarted my docker machine vbox image with 4Gb memory and 2 cpus and left it for an hour or so. The static assets now appear to be present. |
|
I've got exactly same blank page. From my case, i've also seen following errors from stage superset_init: |
That is amazing, i followed you and it worked after one hour waiting for some web packages installations. I've also used WSL2. |
|
I had the same issue, took around 7m for webpack to finish |
|
My guess is that given that the build operation is super io-heavy and that virtualization, depending the platform you're on (say docker on windows, or docker-in-docker, or whatever) can make certain io operations sluggish, and really slow down the build process. Looks like the $ find superset-frontend/node_modules/ | wc -l
240901 |
|
It would be good to have official docker images from the project that don't require you to compile. Any newcomer who wants to try superset has to do all this compilation process to run the project. For anyone who wants to give it a try, here is a link to unofficial docker images: |
I concur. This should be table stakes IMO. |
|
I think I have the same problem I also get This is the logfile: |
|
@nytai Thanks now it's working! I was using the |
|
I have run into this issue, and it worked after installing the latest NPM and node.js. |
|
superset_node container memory up to 4G solve this in my case |
|
I found myself forced to enter to |
|
After increasing Docker memory limits I recreated docker-compose kill superset-node
docker-compose rm superset-node
docker-compose up -d superset-node
|
|
Got the same issue here when I following the official installation guide https://superset.apache.org/docs/installation/installing-superset-using-docker-compose. It's pretty disappointing that having this issue in release/stable versions (I've tried both |
|
I found running |
|
@wahyd4 docker-compose is a dev environment set up. If you'd like to run an official version you can use the pypi distribution, ie This of course means you will have to provide your own metadata database, redis instance, and you will have to configure workers properly in another container. Up to you which set "issues" you're more comfortable dealing with |
|
@nytai Thanks for the clarification and explanation. It does make sense to me. But I suspect many people didn't expect that we have to compile resources when running app via I do acknowledge there is some doc from official website https://superset.apache.org/docs/installation/installing-superset-from-scratch about install superset via |
|
The published docker containers already include the compiled resources. docker-compose volume mounts the repo and sets things up for development purposes, hence why the compilation step is necessary. We could add a version of docker-compose without volume mounts for quickly testing the app out, however that should ideally not be used in prod. The helm chart is also a great way to set up the app quickly for testing but it’s also not ideal for large scale prod deployments as it relies on containerized instances of redis and Postgres. It also expects knowledge of helm charts (most config usually happens in As far as prod deployments, there are so many ways to run a flask app, celery app, celery beat app, provide a database, redis instance, etc. that documenting each would be a huge task. We could point to other resources for deploying flask/celery apps though |
|
@nytai I agree with you that docker-compose shouldn't be used for production ideally, and it provides a super fast way for user to test superset by But I wouldn't agree with your thoughts on Anyway, thanks for the explanation, I have tried the |
|
@wahyd4 Actually, that deperacted helm chart got moved into the superset repo, so all that documentation still applies. If you're up for it, you could open a PR to include that readme in the Additionally, you've inspired me to cook up a docker-compose file explicitly for testing out superset and not developing, #13143 |
Did this solved your issue? Because I am also facing this currently.. |
|
same problem +1 again And I can not see the way to solve this issue in version 3.0.3 |
and others
I am on ubuntu. I am following the instructions to install Superset via docker via this link:
https://superset.incubator.apache.org/installation.html#start-with-docker
Expected results
I expect after these steps if I open http://localhost:8088, I see Superset UI
Actual results
I see a blank page at http://localhost:8088
Screenshots
How to reproduce the bug
Environment
(please complete the following information):
Checklist
Make sure these boxes are checked before submitting your issue - thank you!
Additional context
Here is the full log:
The text was updated successfully, but these errors were encountered: