timbru31 / docker-java-node Goto Github PK

View Code? Open in Web Editor NEW

75.0 4.0 36.0 486 KB

🐳 OpenJDK JRE or JDK (8, 11, 17, 21) with Node.js 18 LTS (Hydrogen) or Node.js 20 LTS (Iron) Docker image

Home Page: https://hub.docker.com/r/timbru31/java-node/

License: MIT License

Dockerfile 100.00%

dockerfile docker node java jre jre8 openjdk openjdk-jre8 jre11 alpine

docker-java-node's Introduction

Java (JRE or JDK version 8, 11, 17 or 21) with Node.js 18 LTS (Hydrogen) or Node.js 20 LTS (Iron) Dockerfile

A minimal Dockerfile based on Eclipse Temurin's OpenJDK JRE or JDK 8/11/17/21 Dockerfile (regular, alpine) with Node.js 18 LTS (Hydrogen) or Node.js 20 LTS (Iron) installed.

What's included

JRE or JDK 8/11/17/21
Node.js 18 LTS (Hydrogen) or Node.js 20 LTS (Iron)
bundled npm that comes with the respective Node.js version (latest for Node.js on alpine, see why)
yarn
curl

Available platforms

These Dockerfiles leverage the new buildx functionality and offer the following platforms:

linux/amd64
linux/arm64 (not for alpine)
linux/arm/v7 (not for alpine, not for Java 21)
linux/ppc64le (not for alpine)

Built by (c) Tim Brust and contributors. Released under the MIT license.

docker-java-node's People

Contributors

Stargazers

Watchers

docker-java-node's Issues

JRE 8u152 @main

Blocked, since upstream is only pointing to JDK 8u141, see https://github.com/docker-library/openjdk/blob/8a23a228bda7d2edeb4132fffd2d08c1e1fcf4ac/8-jdk/Dockerfile#L42

No backwards support

After upgrade to node 10 node 8 images are not more available. Is it possible providing them with some tag, or shall I better do it on my own?

HTTP_PROXY error

I am getting HTTP_PROXY connected to the node-sass. I tried with various tags but getting the same error. Could you please check and advise ?

nodeSetup_1  | Cannot download "https://github.com/sass/node-sass/releases/download/v4.10.0/linux-x64-72_binding.node":
nodeSetup_1  |
nodeSetup_1  | HTTP error 404 Not Found
nodeSetup_1  |
nodeSetup_1  | Hint: If github.com is not accessible in your location
nodeSetup_1  |       try setting a proxy via HTTP_PROXY, e.g.
nodeSetup_1  |
nodeSetup_1  |       export HTTP_PROXY=http://example.com:1234
nodeSetup_1  |
nodeSetup_1  | or configure npm proxy via
nodeSetup_1  |
nodeSetup_1  |       npm config set proxy http://example.com:8080
nodeSetup_1  |
nodeSetup_1  | > [email protected] postinstall /usr/src/script/node_modules/@ionic/app-scripts/node_modules/node-sass
nodeSetup_1  | > node scripts/build.js

Tags with alpine node 14 now use node v16 instead of node v14

I guess due to the version of node in https://dl-cdn.alpinelinux.org/alpine/edge/main/ is now v16

When I use this docker image in the .gitlab-ci.yml, I get an error that yarn cannot be found even though it can find npm. Before running a yarn command I do an apt-get update -qq && apt-get install and that also doesn't make yarn appear. Is there a path exporting I need to do first?

Thanks for the great package!

JRE 11.0.1 @all

How do I reference 17-jre-16-alpine?

I manage to use the 17-jre-16 image, but not the alpine version, how do I use that one, trying this: timbru31/java-node:17-jre-16-alpine?

Java 21 LTS Support

Java 21 LTS is out. It would be awesome if it was added. Thanks!

Add image based on JDK

It would be good to have an image based on a JDK instead of the JRE.

Anyone who has projects that have NPM and Java under the same umbrella could use it!

I can do a PR if you want!

Add Node v16

Node 16 started it's active LTS 26/10/2021 (https://nodejs.org/en/about/releases/)

Can we add tags for node v16 ?

fail to create docker image from timbru31/java-node:11-jdk-14

From the last week it starting to fail, we got the following error when try to create docker image, run from centos 7 (amd64):

15:20:53 Step 1/28 : FROM timbru31/java-node:11-jdk-14 as attbuilder
15:20:53 ---> 171895027082
15:20:53 Step 2/28 : RUN npm install -g node-gyp
15:20:54 ---> Running in a8c1274c96e7
15:20:56 �[91mnode[1]: ../src/node_platform.cc:61:std::unique_ptr node::WorkerThreadsTaskRunner::DelayedTaskScheduler::Start(): Assertion `(0) == (uv_thread_create(t.get(), start_thread, this))' failed.
15:20:56 �[0m�[91m 1: 0xa3aaf0 node::Abort() [node]
15:20:56 �[0m�[91m 2: 0xa3ab6e [node]
15:20:56 �[0m�[91m 3: 0xaab32e [node]
15:20:56 �[0m�[91m 4: 0xaab3f6 node::NodePlatform::NodePlatform(int, v8::TracingController*) [node]
15:20:56 �[0m�[91m 5: 0xa034c6 node::InitializeOncePerProcess(int, char**) [node]
15:20:56 �[0m�[91m 6: 0xa03711 node::Start(int, char**) [node]
15:20:56 7: 0x7fbf4bf26d90 [/lib/x86_64-linux-gnu/libc.so.6]
15:20:56 �[0m�[91m 8: 0x7fbf4bf26e40 __libc_start_main [/lib/x86_64-linux-gnu/libc.so.6]
15:20:56 �[0m�[91m 9: 0x98c58c [node]
15:20:56 �[0mThe command '/bin/bash -o pipefail -c npm install -g node-gyp' returned a non-zero code: 139

Action Required: Fix Renovate Configuration

There is an error with this repository's Renovate configuration that needs to be fixed. As a precaution, Renovate will stop PRs until it is resolved.

Error type: Cannot find preset's package (disableRenovate)

yarn GPG error, invalid signature (workaround with yarn re-install)

Hello! First of all, thank you for the provided image, I recently started using as base image for my build pipelines for a Gradle + Node personal project.

I experienced the following error without build modification:

Reading package lists...
W: GPG error: https://dl.yarnpkg.com/debian stable InRelease: The following signatures were invalid: EXPKEYSIG 23E7166788B63E1E Yarn Packaging <[[email protected]](mailto:[email protected])>
E: The repository 'https://dl.yarnpkg.com/debian stable InRelease' is not signed.

Base image I'm using is timbru31/java-node:11-jdk-12.

Had to re-force an install of yarn, although I see is already done in the Dockerfile

curl -sS https://dl.yarnpkg.com/debian/pubkey.gpg | apt-key add -
echo "deb https://dl.yarnpkg.com/debian/ stable main" | tee /etc/apt/sources.list.d/yarn.list # https://github.com/yarnpkg/yarn/issues/7866
apt-get update && apt-get install -y yarn

Just in case you might want to review the yarn re-installation of the Dockerfile.

Exists the container in case the Test fail

Hi @timbru31 I am using this image to run the protractor tests, however recently it's not working as expected. The container is exiting in case any single test fails with the below error.

Image name - timbru31/java-node:8

nodeSetup_1  | [e2e] [16:59:15] E/launcher - The element reference of <button class="sc-dxgOiQ bYGPLn" type="button"> is stale; either the element is no longer attached to the DOM, it is not in the current frame context, or the document has been refreshed
nodeSetup_1  | [e2e] [16:59:15] E/launcher - StaleElementReferenceError: The element reference of <button class="sc-dxgOiQ bYGPLn" type="button"> is stale; either the element is no longer attached to the DOM, it is not in the current frame context, or the document has been refreshed
nodeSetup_1  | [e2e]     at Object.throwDecodedError (/usr/src/script/node_modules/selenium-webdriver/lib/error.js:514:15)
nodeSetup_1  | [e2e]     at parseHttpResponse (/usr/src/script/node_modules/selenium-webdriver/lib/http.js:519:13)
nodeSetup_1  | [e2e]     at doSend.then.response (/usr/src/script/node_modules/selenium-webdriver/lib/http.js:441:30)
nodeSetup_1  | [e2e]     at process._tickCallback (internal/process/next_tick.js:68:7)
nodeSetup_1  | [e2e] From: Task: WebElement.isEnabled()
nodeSetup_1  | [e2e]     at thenableWebDriverProxy.schedule (/usr/src/script/node_modules/selenium-webdriver/lib/webdriver.js:807:17)
nodeSetup_1  | [e2e]     at WebElement.schedule_ (/usr/src/script/node_modules/selenium-webdriver/lib/webdriver.js:2010:25)
nodeSetup_1  | [e2e]     at WebElement.isEnabled (/usr/src/script/node_modules/selenium-webdriver/lib/webdriver.js:2314:17)
nodeSetup_1  | [e2e]     at actionFn (/usr/src/script/node_modules/protractor/built/element.js:89:44)
nodeSetup_1  | [e2e]     at Array.map (<anonymous>)
nodeSetup_1  | [e2e]     at actionResults.getWebElements.then (/usr/src/script/node_modules/protractor/built/element.js:461:65)
nodeSetup_1  | [e2e]     at ManagedPromise.invokeCallback_ (/usr/src/script/node_modules/selenium-webdriver/lib/promise.js:1376:14)
nodeSetup_1  | [e2e]     at TaskQueue.execute_ (/usr/src/script/node_modules/selenium-webdriver/lib/promise.js:3084:14)
nodeSetup_1  | [e2e]     at TaskQueue.executeNext_ (/usr/src/script/node_modules/selenium-webdriver/lib/promise.js:3067:27)
nodeSetup_1  | [e2e]     at asyncRun (/usr/src/script/node_modules/selenium-webdriver/lib/promise.js:2927:27)Error
nodeSetup_1  | [e2e]     at ElementArrayFinder.applyAction_ (/usr/src/script/node_modules/protractor/built/element.js:459:27)
nodeSetup_1  | [e2e]     at ElementArrayFinder.(anonymous function).args [as isEnabled] (/usr/src/script/node_modules/protractor/built/element.js:91:29)
nodeSetup_1  | [e2e]     at ElementFinder.(anonymous function).args [as isEnabled] (/usr/src/script/node_modules/protractor/built/element.js:831:22)
nodeSetup_1  | [e2e]     at citationPage.po.goToNextStep (/usr/src/script/src/pages/citation.page.js:127:55)
nodeSetup_1  | [e2e] [16:59:15] E/launcher - Process exited with error code 199
nodeSetup_1  | [e2e] npm ERR! code ELIFECYCLE
nodeSetup_1  | [e2e] npm ERR! errno 199
nodeSetup_1  | [e2e] npm ERR! [email protected] e2e: `protractor ./protractor.conf.js`
nodeSetup_1  | [e2e] npm ERR! Exit status 199
nodeSetup_1  | [e2e] npm ERR!
nodeSetup_1  | [e2e] npm ERR! Failed at the [email protected] e2e script.
nodeSetup_1  | [e2e] npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
nodeSetup_1  | [e2e]
nodeSetup_1  | [e2e] npm ERR! A complete log of this run can be found in:
nodeSetup_1  | [e2e] npm ERR!     /root/.npm/_logs/2019-03-11T16_59_15_250Z-debug.log
nodeSetup_1  | [failsafe] Script 'e2e' exited with code 199
nodeSetup_1  | [report]

Question: is it possible to add git?

Hello,

Do you consider adding git to images?

Thanks a lot for your great work and maintaining the project!

Not found javac

When I try node findJavaHome.js , It told that not found: javac

Latest failed build has pushed a failing 11-jre image to docker hub

Hi,

the latest build in Actions has failed: https://github.com/timbru31/docker-java-node/actions/runs/180731795
I believe this has caused the java-node:11-jre to fail in our CI pipeline. We use this image to build our projects.

/usr/bin/docker start 3788f4f4e1fd69f02d081cf990a904e36b77b829d36308bff7803117396eadab
3788f4f4e1fd69f02d081cf990a904e36b77b829d36308bff7803117396eadab
/usr/bin/docker ps --all --filter id=3788f4f4e1fd69f02d081cf990a904e36b77b829d36308bff7803117396eadab --filter status=running --no-trunc --format "{{.ID}} {{.Status}}"
3788f4f4e1fd69f02d081cf990a904e36b77b829d36308bff7803117396eadab Up Less than a second
/usr/bin/docker exec  3788f4f4e1fd69f02d081cf990a904e36b77b829d36308bff7803117396eadab sh -c "command -v bash"
Error response from daemon: Container 3788f4f4e1fd69f02d081cf990a904e36b77b829d36308bff7803117396eadab is not running
##[error]Docker exec fail with exit code 1
##[debug]System.InvalidOperationException: Docker exec fail with exit code 1
   at Microsoft.VisualStudio.Services.Agent.Worker.ContainerOperationProvider.StartContainerAsync(IExecutionContext executionContext, ContainerInfo container)
   at Microsoft.VisualStudio.Services.Agent.Worker.ContainerOperationProvider.StartContainersAsync(IExecutionContext executionContext, Object data)
   at Microsoft.VisualStudio.Services.Agent.Worker.JobExtensionRunner.RunAsync()
   at Microsoft.VisualStudio.Services.Agent.Worker.StepsRunner.RunStepAsync(IStep step, CancellationToken jobCancellationToken)

I'm currently trying out other tags to see if it works any better.

Any chance we run again the build, to restore working images in Docker Hub?

Java 17 LTS support

Update to Node.js v6.11.5 for alpine

fail to create docker image from timbru31/java-node:11-fermium

I try to create my docker image for 11-fermium but I have an error on public key
Docker file:

FROM timbru31/java-node:11-fermium
RUN apt-get -y update \
     && apt-get -y install unzip

Errors:

$ docker build --pull --cache-from $IMAGE_LATEST -t $IMAGE_LATEST .
Sending build context to Docker daemon  36.35kB
Step 1/2 : FROM timbru31/java-node:11-fermium
11-fermium: Pulling from timbru31/java-node
405f018f9d1d: Pulling fs layer
9c045aca8dd9: Pulling fs layer
106421360c5c: Pulling fs layer
0ba[85]ff342cb: Pulling fs layer
626794850eaf: Pulling fs layer
626794850eaf: Waiting
9c045aca8dd9: Verifying Checksum
9c045aca8dd9: Download complete
106421360c5c: Verifying Checksum
106421360c5c: Download complete
405f018f9d1d: Verifying Checksum
405f018f9d1d: Download complete
0ba85ff342cb: Verifying Checksum
0ba85ff342cb: Download complete
626794850eaf: Verifying Checksum
626794850eaf: Download complete
405f018f9d1d: Pull complete
9c045aca8dd9: Pull complete
106421360c5c: Pull complete
0ba85ff342cb: Pull complete
626794850eaf: Pull complete
Digest: sha256:d55e7b1b9befca75fdbc473e01d72262876ea7fbfc96f8518a3faf70bb395a75
Status: Downloaded newer image for timbru31/java-node:11-fermium
 ---> 07de0d20a548
Step 2/2 : RUN apt-get update && apt-get install unzip
 ---> Running in 14e1d8[86]8a0e
Get:1 http://archive.ubuntu.com/ubuntu jammy InRelease [270 kB]
Get:2 https://deb.nodesource.com/node_14.x jammy InRelease [4,563 B]
Get:3 https://dl.yarnpkg.com/debian stable InRelease [17.1 kB]
Get:4 http://archive.ubuntu.com/ubuntu jammy-updates InRelease [109 kB]
Get:5 http://archive.ubuntu.com/ubuntu jammy-backports InRelease [99.8 kB]
Err:2 https://deb.nodesource.com/node_14.x jammy InRelease
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY xxxxxxxxxxxxxxxx
Get:6 http://security.ubuntu.com/ubuntu jammy-security InRelease [110 kB]
Err:3 https://dl.yarnpkg.com/debian stable InRelease
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY xxx
Err:1 http://archive.ubuntu.com/ubuntu jammy InRelease
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY [87]
Err:4 http://archive.ubuntu.com/ubuntu jammy-updates InRelease
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY xxxxx
Err:5 http://archive.ubuntu.com/ubuntu jammy-backports InRelease
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY xxxxx
Err:6 http://security.ubuntu.com/ubuntu jammy-security InRelease
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY x
Reading package lists...
W: GPG error: https://deb.nodesource.com/node_14.x jammy InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 1655A0AB68576280
E: The repository 'https://deb.nodesource.com/node_14.x jammy InRelease' is not signed.
W: https://dl.yarnpkg.com/debian/dists/stable/InRelease: The key(s) in the keyring /etc/apt/trusted.gpg.d/ubuntu-keyring-2012-cdimage.gpg are ignored as the file is not readable by user '_apt' executing apt-key.
W: https://dl.yarnpkg.com/debian/dists/stable/InRelease: The key(s) in the keyring /etc/apt/trusted.gpg.d/ubuntu-keyring-2018-archive.gpg are ignored as the file is not readable by user '_apt' executing apt-key.
W: GPG error: https://dl.yarnpkg.com/debian stable InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 23E71667[88B63E1E
E: The repository 'https://dl.yarnpkg.com/debian stable InRelease' is not signed.
W: http://archive.ubuntu.com/ubuntu/dists/jammy/InRelease: The key(s) in the keyring /etc/apt/trusted.gpg.d/ubuntu-keyring-2012-cdimage.gpg are ignored as the file is not readable by user '_apt' executing apt-key.
W: http://archive.ubuntu.com/ubuntu/dists/jammy/InRelease: The key(s) in the keyring /etc/apt/trusted.gpg.d/ubuntu-keyring-2018-archive.gpg are ignored as the file is not readable by user '_apt' executing apt-key.
W: GPG error: http://archive.ubuntu.com/ubuntu jammy InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 871920D19[91BC93C
E: The repository 'http://archive.ubuntu.com/ubuntu jammy InRelease' is not signed.
W: http://archive.ubuntu.com/ubuntu/dists/jammy-updates/InRelease: The key(s) in the keyring /etc/apt/trusted.gpg.d/ubuntu-keyring-2012-cdimage.gpg are ignored as the file is not readable by user '_apt' executing apt-key.
W: http://archive.ubuntu.com/ubuntu/dists/jammy-updates/InRelease: The key(s) in the keyring /etc/apt/trusted.gpg.d/ubuntu-keyring-2018-archive.gpg are ignored as the file is not readable by user '_apt' executing apt-key.
W: GPG error: http://archive.ubuntu.com/ubuntu jammy-updates InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 871[92]C
E: The repository 'http://archive.ubuntu.com/ubuntu jammy-updates InRelease' is not signed.
W: http://archive.ubuntu.com/ubuntu/dists/jammy-backports/InRelease: The key(s) in the keyring /etc/apt/trusted.gpg.d/ubuntu-keyring-2012-cdimage.gpg are ignored as the file is not readable by user '_apt' executing apt-key.
W: http://archive.ubuntu.com/ubuntu/dists/jammy-backports/InRelease: The key(s) in the keyring /etc/apt/trusted.gpg.d/ubuntu-keyring-2018-archive.gpg are ignored as the file is not readable by user '_apt' executing apt-key.
W: GPG error: http://archive.ubuntu.com/ubuntu jammy-backports InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 871920D1[99]1BC93C
E: The repository 'http://archive.ubuntu.com/ubuntu jammy-backports InRelease' is not signed.
W: http://security.ubuntu.com/ubuntu/dists/jammy-security/InRelease: The key(s) in the keyring /etc/apt/trusted.gpg.d/ubuntu-keyring-2012-cdimage.gpg are ignored as the file is not readable by user '_apt' executing apt-key.
W: http://security.ubuntu.com/ubuntu/dists/jammy-security/InRelease: The key(s) in the keyring /etc/apt/trusted.gpg.d/ubuntu-keyring-2018-archive.gpg are ignored as the file is not readable by user '_apt' executing apt-key.
W: GPG error: http://security.ubuntu.com/ubuntu jammy-security InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 871920D1991BC93C
E: The repository 'http://security.ubuntu.com/ubuntu jammy-security InRelease' is not signed.
E: Problem executing scripts APT::Update::Post-Invoke 'rm -f /var/cache/apt/archives/*.deb /var/cache/apt/archives/partial/*.deb /var/cache/apt/*.bin || true'
E: Sub-process returned an error code
The command '/bin/bash -o pipefail -c apt-get update && apt-get install unzip' returned a non-zero code: [100]

java-node:11-fermium - somewhat elusive

My Dockerfile has this:

FROM timbru31/java-node:11-fermium

And I'm having issues deploying. My issues may be unrelated, but when I Google timbru31/java-node:11-fermium I see this link in the SERPS results:

https://hub.docker.com/layers/timbru31/java-node/11-fermium/images/sha256-5002c0d84dcbc598999aab291b1d634f2481150bc8da6cd3a9950b6b0411a898?context=explore

Which doesn't seem to resolve anything in Docker Hub?

Is there a new way of referring to the image?

Alpine image not correctly updating

Build log:

Building in Docker Cloud's infrastructure...
Cloning into '.'...
Warning: Permanently added the RSA host key for IP address '192.30.253.112' to the list of known hosts.
Reset branch 'master'
Your branch is up-to-date with 'origin/master'.
Pulling cache layers for index.docker.io/timbru31/docker-node-java:alpine...
Done!
KernelVersion: 4.4.0-93-generic
Arch: amd64
BuildTime: 2017-08-17T22:50:04.828747906+00:00
ApiVersion: 1.30
Version: 17.06.1-ce
MinAPIVersion: 1.12
GitCommit: 874a737
Os: linux
GoVersion: go1.8.3
Starting build of index.docker.io/timbru31/docker-node-java:alpine...
Step 1/5 : FROM openjdk:8-jre-alpine
---> 5699ac7295f9
Step 2/5 : LABEL maintainer "Tim Brust <[email protected]>"
---> Using cache
---> 32cb5396c495
Step 3/5 : ENV REFRESHED_AT 2017-10-28
---> Running in 4b42359144ce
---> 379a42a22746
Removing intermediate container 4b42359144ce
Step 4/5 : RUN sed -i -e 's/v3\.4/edge/g' /etc/apk/repositories
---> Running in 347e13ecdb2c
---> 276027933e52
Removing intermediate container 347e13ecdb2c
Step 5/5 : RUN apk add --no-cache nodejs nodejs-npm curl
---> Running in 7de4eebc0370
fetch http://dl-cdn.alpinelinux.org/alpine/v3.6/main/x86_64/APKINDEX.tar.gz
fetch http://dl-cdn.alpinelinux.org/alpine/v3.6/community/x86_64/APKINDEX.tar.gz
(1/9) Installing libssh2 (1.8.0-r1)
(2/9) Installing libcurl (7.56.1-r0)
(3/9) Installing curl (7.56.1-r0)
(4/9) Installing libcrypto1.0 (1.0.2k-r0)
(5/9) Installing http-parser (2.7.1-r1)
(6/9) Installing libssl1.0 (1.0.2k-r0)
(7/9) Installing libuv (1.11.0-r1)
(8/9) Installing nodejs (6.10.3-r1)
(9/9) Installing nodejs-npm (6.10.3-r1)
Executing busybox-1.26.2-r7.trigger
OK: 118 MiB in 59 packages
---> fd4ebbceb8dc
Removing intermediate container 7de4eebc0370
Successfully built fd4ebbceb8dc
Successfully tagged timbru31/docker-node-java:alpine
Pushing index.docker.io/timbru31/docker-node-java:alpine...
Done!
Build finished
Build in 'master:/alpine/Dockerfile' (9d75f1d0) succeeded in 0:01:25�

Implement Docker Best Practices

https://docs.docker.com/engine/userguide/eng-image/dockerfile_best-practices/

Why was slim removed?

Hi, wondering why 11-slim was removed?
beeed48#diff-adb76474a4d21f08634f1141bb92786577a2cca214bc43ea65ebff9b578ea2e2

What is the closest upgrade path from 11-slim?

Thanks.

Integration with pipeline

How can I use this in my nodejs pipeline?
I'm using allure reports with jest but allure needs java so I was looking for packages with both node and java.
Any help would be appreciated.
Thanks

Alpine: JRE8u201/202

Upstream is not yet available - so this is blocked 👎

Node.js v6.11.4 is released

JRE 8u152 @alpine

Blocked since there is actually no alpine release of JRE 8u144 for Alpine v3.6 (nor edge)
Crossref: docker-library/openjdk#138 & docker-library/openjdk#140

standard_init_linux.go:211: exec format on Amazon EC2 arm64 machine

Hello ,

I am using docker in Amazon EC2 machine. Machine info is:

AMI ID
ubuntu/images/hvm-ssd/ubuntu-bionic-18.04-arm64-server

My Dockerfile is:

FROM timbru31/java-node:latest
WORKDIR /app
COPY . .
RUN npm install && npm install -g @angular/cli
EXPOSE ${FM_PORT}
ENTRYPOINT ["node", "--inspect=0.0.0.0:9227", "fmApiStart.js"]

I am getting error like:

Building fm
Step 1/6 : FROM timbru31/java-node:latest
---> d6ffef8c831a
Step 2/6 : WORKDIR /app
---> Running in 14f876ed607f
Removing intermediate container 14f876ed607f
---> 8bb17e94124f
Step 3/6 : COPY . .
---> 30e4f36678f0
Step 4/6 : RUN npm install && npm install -g @angular/cli
---> Running in 612d3b2f7e7f
standard_init_linux.go:211: exec user process caused "exec format error"
ERROR: Service 'fm' failed to build: The command '/bin/bash -o pipefail -c npm install && npm install -g @angular/cli' returned a non-zero code: 1

How can I handle this ?

Thanks

Is it possible to fix the issue so that the image is built with correct version of NodeJS.