richdevboston opened a new issue #9467: Superset fails Docker build using 
"Start with Docker" installation instructions on home page
URL: https://github.com/apache/incubator-superset/issues/9467
 
 
   A clear and concise description of what the bug is.
   
   When I run the installation using Docker according to the instructions 
provided on the Installation and Configuration Page:  ( 
[https://superset.incubator.apache.org/installation.html] ) 
   
   ```
   >> git clone https://github.com/apache/incubator-superset/
   >> cd incubator-superset
   >> docker-compose up
   ```
   
   I get the following result: 
   
   ```
   Step 13/37 : RUN /frontend-mem-nag.sh         && cd /app/superset-frontend   
      && npm ci
    ---> Running in fc57f54ab486
   : No such file or directory
   ERROR: Service 'superset' failed to build: The command '/bin/sh -c 
/frontend-mem-nag.sh         && cd /app/superset-frontend         && npm ci' 
returned a non-zero code: 127
   
   ```
   It does not tell me what file is missing.  
   Is the error referring to the 
   "frontend-mem-nag.sh", the "/app/superset-frontend" or the "npm ci"
    ---> Running in fc57f54ab486
   
   And what does the return code "127" mean?   Is this a permissions problem? 
   
   ### Expected results
   The instructions work.
   
   ### Actual results
   
   docker-compose halts at Step 17/37 with the error above.
   
   #### How to reproduce the bug
   
   Run command above "docker-compose up" at the command line in a Windows 10 
Console with Administrator privileges.  
   
   ### Environment
   
   (please complete the following information):
   
   - superset version: `superset version`  latest 
   - python version: `python --version`   latest v3.6.9 specified in Dockerfile
   - node.js version: `node -v`  latest specified in Dockerfile
   - npm version: `npm -v `specified in Dockerfile
   
   ### Checklist
   
   Make sure these boxes are checked before submitting your issue - thank you!
   
   - [ no - where are the superset logs located?  ] I would have checked the 
superset logs for python stacktraces and included it here as text ( if there 
was a location by the installer given to check)
   - [ yes ] I have reproduced the issue with at least the latest released 
version of superset.
   - [ yes ] I have checked the issue tracker for the same issue and I haven't 
found one similar.
   
   ### Additional context
   
   I am running Windows 10 v1903 (updated yesterday).
   Docker version 19.03.8, build afacb8b
   
   

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