added docker image for 0.3.0; rearranged list of images

Author: fracpete

docker/0.3.0_cpu/Dockerfile

@@ -0,0 +1,20 @@
+FROM ubuntu:22.04
+
+ENV DEBIAN_FRONTEND noninteractive
+RUN apt-get update && \
+    apt-get install -y libglib2.0-0 libsm6 libxrender-dev libxext6 libgl1-mesa-glx git wget && \
+    apt-get install -y build-essential python3-dev python3-venv python3-pip && \
+    apt-get install -y graphviz libgraphviz-dev && \
+    apt-get install -y openjdk-11-jdk && \
+    apt-get clean && \
+    rm -rf /var/lib/apt/lists/*
+
+ENV JAVA_HOME=/usr/lib/jvm/java-11-openjdk-amd64/
+RUN pip3 --no-cache-dir install setuptools wheel && \
+    pip3 --no-cache-dir install python-weka-wrapper3==0.3.0
+
+COPY bash.bashrc /etc/bash.bashrc
+
+ENV WEKA_HOME=/workspace/wekafiles
+WORKDIR /workspace
+RUN chmod 777 /workspace

docker/0.3.0_cpu/README.md

@@ -0,0 +1,72 @@
+# python-weka-wrapper3 Docker (CPU)
+
+## Docker
+
+### Build local image
+
+* Build the image from Docker file (from within `docker/0.3.0_cpu`)
+
+  ```bash
+  docker build -t pww3_cpu .
+  ```
+  
+* Run the container
+
+  ```bash
+  docker run -v /local/dir:/container/dir -it pww3_cpu
+  ```
+  `/local/dir:/container/dir` maps a local disk directory into a directory inside the container
+
+## Pre-built images
+
+* Build
+
+  ```bash
+  docker build -t pww3:0.3.0_cpu .
+  ```
+  
+* Tag
+
+  ```bash
+  docker tag \
+    pww3:0.3.0_cpu \
+    fracpete/pww3:0.3.0_cpu
+  ```
+  
+* Push
+
+  ```bash
+  docker push fracpete/pww3:0.3.0_cpu
+  ```
+
+### Special directories
+
+* `/workspace/wekafiles` - the directory that `WEKA_HOME` is pointing to (packages, props files, etc) 
+
+
+## Usage
+
+### Basic
+
+For using the image interactively, you can run the following command: 
+
+```bash
+docker run -u $(id -u):$(id -g) \
+    -it fracpete/pww3:0.3.0_cpu
+```
+
+**NB:** Use `-v localdir:containerdir` to map directories from your host into the container.
+
+### With local packages
+
+Instead of having to reinstall your packages each time you start up the container, 
+you can map your local Weka packages into the container as follows: 
+
+```bash
+docker run -u $(id -u):$(id -g) \
+    -v $HOME/wekafiles/:/workspace/wekafiles \
+    -it fracpete/pww3:0.3.0_cpu
+```
+
+**NB:** That way, you can separate various package installations on your host system
+in different directories.

docker/0.3.0_cpu/bash.bashrc

@@ -0,0 +1,54 @@
+# Copyright 2018 The TensorFlow Authors. All Rights Reserved.
+# Copyright 2020 University of Waikato, Hamilton, NZ. All Rights Reserved.
+#
+# Licensed under the Apache License, Version 2.0 (the "License");
+# you may not use this file except in compliance with the License.
+# You may obtain a copy of the License at
+#
+#     http://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing, software
+# distributed under the License is distributed on an "AS IS" BASIS,
+# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+# See the License for the specific language governing permissions and
+# limitations under the License.
+#
+# ==============================================================================
+
+export PS1="\[\e[31m\]docker\[\e[m\] \[\e[33m\]\w\[\e[m\] > "
+export TERM=xterm-256color
+alias grep="grep --color=auto"
+alias ls="ls --color=auto"
+
+echo -e "\e[1;31m"
+cat<<DBG
+                         _____ 
+ _ ____      ____      _|___ / 
+| '_ \\ \\ /\\ / /\\ \\ /\\ / / |_ \\ 
+| |_) \\ V  V /  \\ V  V / ___) |
+| .__/ \\_/\\_/    \\_/\\_/ |____/ 
+|_|                            
+
+0.3.0, OpenJDK 11, Python 3.10
+
+DBG
+echo -e "\e[0;33m"
+
+if [[ $EUID -eq 0 ]]; then
+  cat <<WARN
+WARNING: You are running this container as root, which can cause new files in
+mounted volumes to be created as the root user on your host machine.
+
+To avoid this, run the container by specifying your user's userid:
+
+$ docker run -u \$(id -u):\$(id -g) args...
+WARN
+else
+  cat <<EXPL
+You are running this container as user with ID $(id -u) and group $(id -g),
+which should map to the ID and group for your user on the Docker host. Great!
+EXPL
+fi
+
+# Turn off colors
+echo -e "\e[m"

docker/README.md

@@ -1,50 +1,23 @@
 # Docker
 
 In order to make installation reproducible, the following Docker images 
-(which can be used interactively) are maintained:
-
-* 0.2.16
-  
-  * [CPU only](0.2.16_cpu)
-
-* 0.2.15
-  
-  * [CPU only](0.2.15_cpu)
-
-* 0.2.14
-  
-  * [CPU only](0.2.14_cpu)
-  * [CUDA 10.2](0.2.14_cuda10.2)
-
-* 0.2.13
-  
-  * [CPU only](0.2.13_cpu)
-  * [CUDA 10.2](0.2.13_cuda10.2)
-
-* 0.2.12
-  
-  * [CPU only](0.2.12_cpu)
-  * [CUDA 10.2](0.2.12_cuda10.2)
-
-* 0.2.11
-  
-  * [CPU only](0.2.11_cpu)
-  * [CUDA 10.2](0.2.11_cuda10.2)
-
-* 0.2.10
-  
-  * [CPU only](0.2.10_cpu)
-  * [CUDA 10.2](0.2.10_cuda10.2)
-
-* 0.2.9
-  
-  * [CPU only](0.2.9_cpu)
-  * [CUDA 10.2](0.2.9_cuda10.2)
-
-* 0.2.8
-  
-  * [CPU only](0.2.8_cpu)
-  * [CUDA 10.2](0.2.8_cuda10.2)
+(which can be used interactively) are maintained.
+
+jpype-based:
+
+* 0.3.0 ([CPU only](0.3.0_cpu))
+
+javabridge-based:
+
+* 0.2.16 ([CPU only](0.2.16_cpu))
+* 0.2.15 ([CPU only](0.2.15_cpu))
+* 0.2.14 ([CPU only](0.2.14_cpu), [CUDA 10.2](0.2.14_cuda10.2))
+* 0.2.13 ([CPU only](0.2.13_cpu), [CUDA 10.2](0.2.13_cuda10.2))
+* 0.2.12 ([CPU only](0.2.12_cpu), [CUDA 10.2](0.2.12_cuda10.2))
+* 0.2.11 ([CPU only](0.2.11_cpu), [CUDA 10.2](0.2.11_cuda10.2))
+* 0.2.10 ([CPU only](0.2.10_cpu), [CUDA 10.2](0.2.10_cuda10.2))
+* 0.2.9 ([CPU only](0.2.9_cpu), [CUDA 10.2](0.2.9_cuda10.2))
+* 0.2.8 ([CPU only](0.2.8_cpu), [CUDA 10.2](0.2.8_cuda10.2))
 
 The images themselves are available through Docker hub: