Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Fail to build with Docker compose.

See original GitHub issue

Issue Summary

A summary of the issue and the browser/OS environment in which it occurs. Windows 10 - Docker.

Steps to Reproduce

This is the first step https://redash.io/help/open-source/dev-guide/docker I’m just trying to use the latest commit to test Dgraph. But there’s errors blocking me. I can’t build master.

PS C:\Users\micheldiz\Github\redash> docker-compose up -d
Building server
Step 1/18 : FROM node:10 as frontend-builder
 ---> 9b9d314e0a86
Step 2/18 : WORKDIR /frontend
 ---> Using cache
 ---> 2c645ddf9629
Step 3/18 : COPY package.json package-lock.json /frontend/
 ---> Using cache
 ---> 631129efb8ff
Step 4/18 : RUN npm install
 ---> Using cache
 ---> dbaf1e09129b
Step 5/18 : COPY client /frontend/client
 ---> Using cache
 ---> 91c15008e412
Step 6/18 : COPY webpack.config.js /frontend/
 ---> Using cache
 ---> b9260b7b6ab9
Step 7/18 : RUN npm run build
 ---> Running in 456213d01247

> redash-client@8.0.0-beta build /frontend
> npm run clean && NODE_ENV=production node --max-old-space-size=4096 node_modules/.bin/webpack


> redash-client@8.0.0-beta clean /frontend
> rm -rf ./client/dist/

Browserslist: caniuse-lite is outdated. Please run next command `npm update caniuse-lite browserslist`
Killed
npm ERR! code ELIFECYCLE
npm ERR! errno 137
npm ERR! redash-client@8.0.0-beta build: `npm run clean && NODE_ENV=production node --max-old-space-size=4096 node_modules/.bin/webpack`
npm ERR! Exit status 137
npm ERR! 
npm ERR! Failed at the redash-client@8.0.0-beta build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2019-08-13T18_03_47_394Z-debug.log
ERROR: Service 'server' failed to build: The command '/bin/sh -c npm run build' returned a non-zero code: 137

Issue Analytics

State:
Created 4 years ago
Comments:7 (4 by maintainers)

Top GitHub Comments

1reaction

arikfrcommented, Aug 14, 2019

You probably need to allocate more memory to your Docker VM.

But if you just want to test the Dgraph connection, you can use the redash/redash:preview Docker image, which tracks the master branch and has Dgraph support.

0reactions

MichelDizcommented, Aug 15, 2019

I’ve no luck at all. I’ve increased the RAM. It went a little further. But fails. After that video I gave 21 GB of RAM and the error keeps going.

I’ve also tried start from scratch doing docker prune commands.

https://youtu.be/4fQzW59VAZc

Top Results From Across the Web

Why does building and image with docker compose fail but ...

I am trying to build an image with docker compose and it fails, however it works with just docker. I have read some...

Unable to build dockerfile via docker-compose

Hi,. I recognized a very strange behavior of my docker-compose: Here come a minimal (not) working example: This is my docker-compose.yml:

docker compose build failed · Issue #9405 - GitHub

It seems to be caused by setting usersns-remap , I have two vps with usersns-remap set to default , all of them build...

Solution build fails with docker compose error (in VS 15.3)

Developer Community. We have solution with docker enabled projects. It works if remove nginx service from docker-compose. yml and fails if return nginx...

Fail to build images with docker compose - CircleCI Discuss

Currently, using docker compose to build an image fails with this error: listing workers for Build: failed to list workers: Unavailable: ...