Segmentation fault on Windows

[LeNouveau]

Hi,

When building the following Dockerfile on Windows 10, I have a Segmentation fault error.

FROM node:wheezy
RUN yarn global add typescript @angular/cli 

Doesn't seems to be related to yarn, as npm gives the same result :

FROM node:wheezy
RUN npm install -g typescript @angular/cli

The result is :

C:\Users\toto\myProject>docker build .
Sending build context to Docker daemon  37.23MB
Step 1/2 : FROM node:wheezy
 ---> d8df1e668586
Step 2/2 : RUN npm install -g typescript @angular/cli
 ---> Running in 45c9b17ed77e
Segmentation fault
The command '/bin/sh -c npm install -g typescript @angular/cli' returned a non-zero code: 139

My configuration :

• docker --version : Docker version 17.10.0-ce, build f4ffd25
• Windows 10 Pro

I tried on a Fedora server, its works like a charm.
(unfortunatly, W10 is required)

So, is it a wanted behaviour ?

[SimenB]

It's definitely not desired behavior. That said, it seems more like a general Docker issue than an issue with the Node.js image. Have you tried asking at any of the channels listed here: https://docs.docker.com/opensource/get-help/?

[LeNouveau]

Seems very related to your image, with npm and yarn commands.
If I pick another version, for exemple node:latest or node:alpin, I don't have this kind of error.

Exemple Dockerfile

FROM node:wheezy
RUN uname -a
RUN pwd
RUN node --version
RUN npm --version

Result :

C:\Users\toto\myProject>docker build .
Sending build context to Docker daemon  37.32MB
Step 1/4 : FROM node:wheezy
 ---> d8df1e668586
Step 2/5 : RUN uname -a
 ---> Running in 8b5e3394a19f
Linux 8b5e3394a19f 4.9.44-linuxkit-aufs #1 SMP Fri Aug 25 10:00:41 UTC 2017 x86_64 GNU/Linux
 ---> 9b8d689abf15
Step 3/5 : RUN pwd
 ---> Running in fa7a9ffe1c48
/
 ---> 6977ae2041d4
Step 4/5 : RUN node --version
 ---> Running in af0113e60939
v8.7.0
 ---> d85907525d60
Step 5/5 : RUN npm --version
 ---> Running in 0957afaa6c7d
Segmentation fault
The command '/bin/sh -c npm --version' returned a non-zero code: 139

So, still think it's a general Docker issue ?

[LaurentGoderre]

To me it looks like a Windows 10 Docker issue

[chorrell]

This only seems to happen on the wheezy variant, according to the OP, but works for other versions.

We will be dropping the wheezy variant soon so I would recommend using either node:8 or node:alpine-8 (assuming you are fine with using Node.js 8.x.x.):

#567

[chorrell]

Closing since it's either an issue with a variant we will be dropping, an issue with Docker on Windows 10 or some combination of both.