Ecosyste.ms: Awesome

An open API service indexing awesome lists of open source software.

Awesome Lists | Featured Topics | Projects

https://github.com/drsnowbird/jdk-mvn-py3

Ubuntu 24.04 + OpenJDK Java 23 + Maven 3.9 + Python 3.12 + pip 23 + node 21 + npm 10 + Yarn + Gradle 7
https://github.com/drsnowbird/jdk-mvn-py3

docker gradle java maven node-js npm-package openjdk python3 websocket

Last synced: 24 days ago
JSON representation

Ubuntu 24.04 + OpenJDK Java 23 + Maven 3.9 + Python 3.12 + pip 23 + node 21 + npm 10 + Yarn + Gradle 7

Awesome Lists containing this project

README 

        
# OpenJDK Java 23 + Maven 3.9 + Python 3.12  + pip 23 + node 21 + npm 10 + Yarn + Gradle 7



[![](https://images.microbadger.com/badges/image/openkbs/jdk-mvn-py3.svg)](https://microbadger.com/images/openkbs/jdk-mvn-py3 "Get your own image badge on microbadger.com") [![](https://images.microbadger.com/badges/version/openkbs/jdk-mvn-py3.svg)](https://microbadger.com/images/openkbs/jdk-mvn-py3 "Get your own version badge on microbadger.com")



# ** Currently Docker Hub not allowing free hosting for Docker images: Please run ./build.sh first by yourself locally **



`(**NEW**) Updated to latest Ubuntu 24.04 and related latest tools, e.g., pip, Maven, Python, Java, etc.`



# NOTICE: Change to use `Non-Root` implementation

This new release is designed to support the deployment for Non-Root child images implementations and deployments to platform such as OpenShift or RedHat host operating system which requiring special policy to deploy. And, for better security practice, we decided to migrate (eventaully) our Docker containers to use Non-Root implementation. 

Here are some of the things you can do if your images requiring "Root" acccess - you `really` want to do it:

1. For Docker build: Use "sudo" or "sudo -H" prefix to your Dockerfile's command which requiring "sudo" access to install packages.

2. For Docker container (access via shell): Use "sudo" command when you need to access root privilges to install packages or change configurations.

3. Or, you can use older version of this kind of base images which use "root" in Dockerfile.

4. Yet, you can also modify the Dockerfile at the very bottom to remove/comment out the "USER ${USER}" line so that your child images can have root as USER.

5. Finally, you can also, add a new line at the very top of your child Docker image's Dockerfile to include "USER root" so that your Docker images built will be using "root".



We like to promote the use of "Non-Root" images as better Docker security practice. And, whenever possible, you also want to further confine the use of "root" privilges in your Docker implementation so that it can prevent the "rooting hacking into your Host system". To lock down your docker images and/or this base image, you will add the following line at the very end to remove sudo: `(Notice that this might break some of your run-time code if you use sudo during run-time)`

```

sudo agt-get remove -y sudo

```

After that, combining with other Docker security practice (see below references), you just re-build your local images and re-deploy it as non-development quality of docker container. However, there are many other practices to secure your Docker containes. See below:



* [Docker security | Docker Documentation](https://docs.docker.com/engine/security/security/)

* [5 tips for securing your Docker containers - TechRepublic](https://www.techrepublic.com/article/5-tips-for-securing-your-docker-containers/)

* [Docker Security - 6 Ways to Secure Your Docker Containers](https://www.sumologic.com/blog/security/securing-docker-containers/)

* [Five Docker Security Best Practices - The New Stack](https://thenewstack.io/5-docker-security-best-practices/)



# Components

* Ubuntu 24.04 now.

* openjdk version "23-ea" 2024-09-17

  OpenJDK Runtime Environment (build 23-ea+10-Ubuntu-1)

  OpenJDK 64-Bit Server VM (build 23-ea+10-Ubuntu-1, mixed mode, sharing)

* Apache Maven 3.9

* Python 3.12 + pip 23 + Python 3 virtual environments (venv, virtualenv, virtualenvwrapper, mkvirtualenv, ..., etc.)

* Node v21 + npm 10 (from NodeSource official Node Distribution)

* Gradle 7

* Other tools: git wget unzip vim python python-setuptools python-dev python-numpy, ..., etc.

* [See Releases Information](https://github.com/DrSnowbird/jdk-mvn-py3/blob/master/README.md#Releases-information)

* Note: 'yarn' is removed from this latest build -- if needed, it will be put back later releases.



# Quick commands

* build.sh - build local image.

* logs.sh - see logs of container.

* run.sh - run the container.

* shell.sh - shell into the container.

* save.sh - save a running Container instance into a tgz file for later to restore.

* restore.sh - restore the previously archived tgz Container instance ready for running again.

* stop.sh - stop the container.

* tryJava.sh : test Java

* tryNodeJS.sh : test NodeJS

* tryPython.sh : test Python

* tryWebSocketServer.sh : test WebSockert NodeJS Server



# How to use and quick start running?

1. git clone https://github.com/DrSnowbird/jdk-mvn-py3.git

2. cd jdk-mvn-py3

3. ./run.sh



# Default Run (test) - Just entering Container

```

./build.sh or 'make build'

./run.sh

```



# Test Java, NodeJS, and Python3 Runs

```

./tryJava.sh

./tryNodeJS.sh

./tryPython.sh

./tryWebSockerServer.sh

```

* Issue: the `./tryJava.sh` encouters some permission to write share folder in Container. To fix later!



# Default Build (locally)

```

./build.sh

```

# Pull the image from Docker Repository



```bash

docker pull openkbs/jdk-mvn-py3

```



# Base the image to build add-on components



```Dockerfile

FROM openkbs/jdk-mvn-py3

... (then your customization Dockerfile code here)

```



# Manually setup to Run the image



Then, you're ready to run:

- make sure you create your work directory, e.g., ./data



```bash

mkdir ./data

docker run -d --name my-jdk-mvn-py3 -v $PWD/data:/data -i -t openkbs/jdk-mvn-py3

```



# Build and Run your own image

Say, you will build the image "my/jdk-mvn-py3".



```bash

docker build -t my/jdk-mvn-py3 .

```



To run your own image, say, with some-jdk-mvn-py3:



```bash

mkdir ./data

docker run -d --name some-jdk-mvn-py3 -v $PWD/data:/data -i -t my/jdk-mvn-py3

```



# Shell into the Docker instance



```bash

docker exec -it some-jdk-mvn-py3 /bin/bash

```



# Run Python code



To run Python code 



```bash

docker run -it --rm openkbs/jdk-mvn-py3 python3 -c 'print("Hello World")'

```



or,



```bash

docker run -i --rm openkbs/jdk-mvn-py3 python3 < myPyScript.py 

```



or,



```bash

mkdir ./data

echo "print('Hello World')" > ./data/myPyScript.py

docker run -it --rm --name some-jdk-mvn-py3 -v "$PWD"/data:/data openkbs/jdk-mvn-py3 python3 myPyScript.py

```



or,



```bash

alias dpy3='docker run --rm openkbs/jdk-mvn-py3 python3'

dpy3 -c 'print("Hello World")'

```



# Compile or Run java -- while no local installation needed

Remember, the default working directory, /data, inside the docker container -- treat is as "/".

So, if you create subdirectory, "./data/workspace", in the host machine and 

the docker container will have it as "/data/workspace".



```

#!/bin/bash -x

mkdir ./data

cat >./data/HelloWorld.java <<-EOF

public class HelloWorld {

   public static void main(String[] args) {

      System.out.println("Hello, World");

   }

}

EOF

cat ./data/HelloWorld.java

alias djavac='docker run -it --rm --name some-jdk-mvn-py3 -v '$PWD'/data:/data openkbs/jdk-mvn-py3 javac'

alias djava='docker run -it --rm --name some-jdk-mvn-py3 -v '$PWD'/data:/data openkbs/jdk-mvn-py3 java'

djavac HelloWorld.java

djava HelloWorld

```

And, the output:

```

Hello, World

```

Hence, the alias above, "djavac" and "djava" is your docker-based "javac" and "java" commands and 

it will work the same way as your local installed Java's "javac" and "java" commands. 



# Run JavaScript -- while no local installation needed

Run the NodeJS mini-server script:

```

./tryNodeJS.sh

```

Then, open web browser to go to http://0.0.0.0:3000/ to NodeJS mini-web server test.



# Python Virtual Environments

There are various ways to run Python virtual envrionments, for example,



### Setup virtualenvwrapper in $HOME/.bashrc profile

Add the following code to the end of ~/.bashrc

```

#########################################################################

#### ---- Customization for multiple virtual python environment ---- ####

#########################################################################

export VIRTUALENVWRAPPER_PYTHON=/usr/bin/python3

source /usr/local/bin/virtualenvwrapper.sh

export WORKON_HOME=~/Envs

if [ ! -d $WORKON_HOME ]; then

    mkdir -p $WORKON_HOME

fi

```



### To create & activate your default venv environment, say, "my-venv":

```

mkvirtualenv my-venv

workon my-venv

```



# To run specialty Java/Scala IDE alternatives

However, for larger complex projects, you might want to consider to use Docker-based IDE. 

For example, try the following Docker-based IDEs:

* [openkbs/docker-atom-editor](https://hub.docker.com/r/openkbs/docker-atom-editor/)

* [openkbs/eclipse-photon-docker](https://hub.docker.com/r/openkbs/eclipse-photon-docker/)

* [openkbs/eclipse-photon-vnc-docker](https://hub.docker.com/r/openkbs/eclipse-photon-vnc-docker/)

* [openkbs/eclipse-oxygen-docker](https://hub.docker.com/r/openkbs/eclipse-oxygen-docker/)

* [openkbs/intellj-docker](https://hub.docker.com/r/openkbs/intellij-docker/)

* [openkbs/intellj-vnc-docker](https://hub.docker.com/r/openkbs/intellij-vnc-docker/)

* [openkbs/knime-vnc-docker](https://hub.docker.com/r/openkbs/knime-vnc-docker/)

* [openkbs/netbeans9-docker](https://hub.docker.com/r/openkbs/netbeans9-docker/)

* [openkbs/netbeans](https://hub.docker.com/r/openkbs/netbeans/)

* [openkbs/papyrus-sysml-docker](https://hub.docker.com/r/openkbs/papyrus-sysml-docker/)

* [openkbs/pycharm-docker](https://hub.docker.com/r/openkbs/pycharm-docker/)

* [openkbs/scala-ide-docker](https://hub.docker.com/r/openkbs/scala-ide-docker/)

* [openkbs/sublime-docker](https://hub.docker.com/r/openkbs/sublime-docker/)

* [openkbs/webstorm-docker](https://hub.docker.com/r/openkbs/webstorm-docker/)

* [openkbs/webstorm-vnc-docker](https://hub.docker.com/r/openkbs/webstorm-vnc-docker/)



# See also

* [Java Development in Docker](https://blog.giantswarm.io/getting-started-with-java-development-on-docker/)

* [Alpine small image JDKs](https://github.com/frol/docker-alpine-oraclejdk8)

* [NPM Prefix for not using SUDO NPM](https://docs.npmjs.com/resolving-eacces-permissions-errors-when-installing-packages-globally)



# Proxy & Certificate Setup

* [Setup System and Browsers Root Certificate](https://thomas-leister.de/en/how-to-import-ca-root-certificate/)



# Corporate Proxy Root and Intemediate Certificates setup for System and Web Browsers (FireFox, Chrome, etc)

1. Save your corporate's Certificates in the currnet GIT directory, `./certificates`

2. During Docker run command, 

```

   -v `pwd`/certificates:/certificates ... (the rest parameters)

```

If you want to map to different directory for certificates, e.g., /home/developer/certificates, then

```

   -v `pwd`/certificates:/home/developer/certificates -e SOURCE_CERTIFICATES_DIR=/home/developer/certificates ... (the rest parameters)

```

3. And, inside the Docker startup script to invoke the `~/scripts/setup_system_certificates.sh`. Note that the script assumes the certficates are in `/certificates` directory.

4. The script `~/scripts/setup_system_certificates.sh` will automatic copy to target directory and setup certificates for both System commands (wget, curl, etc) to use and Web Browsers'.



# Releases information

```

~$ /usr/scripts/printVersions.sh 

JAVA_HOME=/usr/lib/jvm/java-23-openjdk-amd64

java: /usr/bin/java /usr/share/java /usr/lib/jvm/java-23-openjdk-amd64/bin/java /usr/share/man/man1/java.1.gz



/usr/lib/jvm/java-23-openjdk-amd64/bin/java

openjdk version "23-ea" 2024-09-17

OpenJDK Runtime Environment (build 23-ea+10-Ubuntu-1)

OpenJDK 64-Bit Server VM (build 23-ea+10-Ubuntu-1, mixed mode, sharing)

/usr/bin/mvn

Apache Maven 3.9.6 (bc0240f3c744dd6b6ec2920b3cd08dcc295161ae)

Maven home: /usr/apache-maven-3.9.6

Java version: 23-ea, vendor: Private Build, runtime: /usr/lib/jvm/java-23-openjdk-amd64

Default locale: en, platform encoding: UTF-8

OS name: "linux", version: "6.5.0-21-generic", arch: "amd64", family: "unix"

/usr/bin/python3

Python 3.12.2

/usr/bin/pip

pip 23.3 from /usr/lib/python3/dist-packages/pip (python 3.12)

/usr/bin/pip3

pip 23.3 from /usr/lib/python3/dist-packages/pip (python 3.12)

/usr/bin/gradle



Welcome to Gradle 7.6.4!



Here are the highlights of this release:

 - Added support for Java 19.

 - Introduced `--rerun` flag for individual task rerun.

 - Improved dependency block for test suites to be strongly typed.

 - Added a pluggable system for Java toolchains provisioning.



For more details see https://docs.gradle.org/7.6.4/release-notes.html



------------------------------------------------------------

Gradle 7.6.4

------------------------------------------------------------



Build time:   2024-02-05 14:29:18 UTC

Revision:     e0bb3fc8cefad8432c9033cdfb12dc14facc9dd9



Kotlin:       1.7.10

Groovy:       3.0.13

Ant:          Apache Ant(TM) version 1.10.13 compiled on January 4 2023

JVM:          23-ea (Private Build 23-ea+10-Ubuntu-1)

OS:           Linux 6.5.0-21-generic amd64



/usr/bin/npm

10.2.4

/usr/bin/node

v21.6.2

DISTRIB_ID=Ubuntu

DISTRIB_RELEASE=24.04

DISTRIB_CODENAME=noble

DISTRIB_DESCRIPTION="Ubuntu Noble Numbat (development branch)"

PRETTY_NAME="Ubuntu Noble Numbat (development branch)"

NAME="Ubuntu"

VERSION_ID="24.04"

VERSION="24.04 (Noble Numbat)"

VERSION_CODENAME=noble

ID=ubuntu

ID_LIKE=debian

HOME_URL="https://www.ubuntu.com/"

SUPPORT_URL="https://help.ubuntu.com/"

BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"

PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"

UBUNTU_CODENAME=noble

LOGO=ubuntu-logo

```