superset-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From GitBox <>
Subject [GitHub] [incubator-superset] yanickrochon opened a new issue #9711: Memory Insufficient Warning with docker
Date Fri, 01 May 2020 20:33:57 GMT

yanickrochon opened a new issue #9711:

   On a VM wich initially ran with only 1 GB of RAM, I increased that amount to 4 GB, installed
docker and other requirements, then ran `docker-composer up`, as indicated on the [Installation
& Configuration]( page. But after
downloading  5.2 GB of stuff, I get this message
   Step 13/37 : RUN /         && cd /app/superset-frontend    
    && npm ci
    ---> Running in e18f62b44119
       ========  Memory Insufficient Warning =========
       It looks like you only have 0.284832 GB of
       memory free. Please increase your Docker
       resources to at least 3GB
       ========  Memory Insufficient Warning =========
   npm ERR! network timeout at:
   npm ERR! A complete log of this run can be found in:
   npm ERR!     /root/.npm/_logs/2020-05-01T20_06_18_860Z-debug.log
   ERROR: Service 'superset' failed to build: The command '/bin/sh -c /
        && cd /app/superset-frontend         && npm ci' returned a non-zero
code: 1
   ### Expected results
   The process should use the available memory
   $ free
                 total        used        free      shared  buff/cache   available
   Mem:        4041492      401264      513704        6940     3126524     3344720
   Swap:       1046524        6412     1040112
   ### Actual results
   Not enough memory (for some reason)
   ### Environment
   - superset version: as of May 1st 2020 (seriously, where can I find the version number?)
   - python version: `3.7.3`
   - node.js version: `12.10.0`
   - npm version: `6.14.4`
   ### Checklist
   Make sure these boxes are checked before submitting your issue - thank you!
   - [x] I have checked the superset logs for python stacktraces and included it here as text
if there are any.
   - [x] I have reproduced the issue with at least the latest released version of superset.
   - [x] I have checked the issue tracker for the same issue and I haven't found one similar.

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:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message