You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Platform: Linux 71c9818f32be 4.19.76-linuxkit #1 SMP Tue May 26 11:42:35 UTC 2020 x86_64 Linux
Subsystem: ? (build?, test?)
What steps will reproduce the bug?
Dockerfile (execute using docker build --build-arg NODE_VERSION=14.4.0 .):
FROM alpine:3.12.0 AS build
ARG NODE_VERSION
RUN apk update && apk upgrade -a
RUN apk add \
build-base \
curl \
gnupg \
linux-headers \
make \
python3
# gpg keys from https://github.com/nodejs/node#release-keys
RUN for key in \
4ED778F539E3634C779C87C6D7062848A1AB005C \
B9E2F5981AA6E0CD28160D9FF13993A75599653C \
94AE36675C464D64BAFA68DD7434390BDBE9B9C5 \
B9AE9905FFD7803F25714661B63B535A4C206CA9 \
77984A986EBC2AA786BC0F66B01FBB92821C587A \
71DCFD284A79C3B38668286BC97EC7A07EDE3FC1 \
FD3A5288F042B6850C66B31F09FE44734EB7990E \
8FCCA13FEF1D0C2E91008E09770F7A9A5AE15600 \
C4F0DFFF4E8C1A8236409D08E73BC641CC11F4C8 \
DD8F2338BAE7501E3DD5AC78C273792F7D83545D \
A48C2BEE680E841632CD4E44F07496B3EB3C1762 \
; do \
gpg --keyserver ha.pool.sks-keyservers.net --recv-keys "$key" || \
gpg --keyserver pgp.mit.edu --recv-keys "$key" || \
gpg --keyserver keyserver.pgp.com --recv-keys "$key"; \
done
RUN curl -SLO "https://nodejs.org/dist/v$NODE_VERSION/node-v$NODE_VERSION.tar.xz"
RUN curl -SLO --compressed "https://nodejs.org/dist/v$NODE_VERSION/SHASUMS256.txt.asc"
RUN gpg --batch --decrypt --output SHASUMS256.txt SHASUMS256.txt.asc
RUN grep " node-v$NODE_VERSION.tar.xz\$" SHASUMS256.txt | sha256sum -c -
RUN tar -xf "node-v$NODE_VERSION.tar.xz"
WORKDIR "node-v$NODE_VERSION"
RUN uname -a
RUN ./configure --prefix /opt/node
RUN make -j$(getconf _NPROCESSORS_ONLN)
RUN make install
RUN make test
How often does it reproduce? Is there a required condition?
This is the same as #33762 — historically we have stripped out things from the source tarball for space reasons. Let’s keep the discussion over there as to whether that still makes sense.
v14.4.0
Linux 71c9818f32be 4.19.76-linuxkit #1 SMP Tue May 26 11:42:35 UTC 2020 x86_64 Linux
What steps will reproduce the bug?
Dockerfile
(execute usingdocker build --build-arg NODE_VERSION=14.4.0 .
):How often does it reproduce? Is there a required condition?
2 of 2 attempted builds.
What is the expected behavior?
Successful compilation and tests.
What do you see instead?
full output: output.txt
Additional information
The text was updated successfully, but these errors were encountered: