vdmitriyev commented on issue #8632: docker-compose  failed to build
URL: 
https://github.com/apache/incubator-superset/issues/8632#issuecomment-559146183
 
 
   @lyy8510a I had the same issue. The advice of the @zhouyao1994 helped me. 
Actually, I was not doing anything else, other than applying the commands 
suggested by @zhouyao1994.
   
   * However, in my case by the very first installation of the VM I used not 
that much resources. My VM - Ubuntu 18.04 LTS, installed via vagrant on Windows 
host. 
   * Then I added more resources to the VM (RAM - 4 Gb, CPU - 2x), but still 
experienced the same problem. 
   * Then I increased size of the swap to 1GB, as it was suggested 
[here](http://www.inanzzz.com/index.php/post/gz4x/preventing-composer-crash-in-vagrant-proc-open-fork-failed-cannot-allocate-memory).
 
   * But even after adding more resources, the installation didn't succeed. 
   * Then I restarted VM, stopped all containers, and removed them via ```sudo 
docker system prune``` and made sure that all previous containers were removed.
   * Then navigated to the ```<YOUR-PATH>/incubator-superset/contrib/docker/``` 
and run ```sudo docker-compose run -e SUPERSET_LOAD_EXAMPLES=yes --rm superset 
./docker-init.sh``` (as suggested by @zhouyao1994). And after waiting for a 
while and typing in admin login the installation was successfully completed!
   * As the last step, I run the containers manually via ```sudo docker-compose 
up``` 
   
   I hope it helps you.

----------------------------------------------------------------
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]


With regards,
Apache Git Services

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to