Fast Start

You need docker desktop (or run it on a cloud provider's infrastructure).

Then:

docker pull adriansutherland/vm370:latest
docker run --rm -d -p 3270:3270 -p 8038:8038 -p 3505:3505 --name vm370 adriansutherland/vm370:latest

(so the dockerhub page is https://hub.docker.com/repository/docker/adriansutherland/vm370)

Notes:

• first download is slow, after that it uses a cache

• the --rm option deletes the container (and DASD changes) when Hercules exits. You may want to miss out that option if you want to re-launch the specific container instance and save your DASD change etc.!!

• you can connect to localhost:3270 for 3270; 8038 for web console, 3505 for card reader

• It is setup to start Hercules but it does not ipl - so IPL 141 at the console.

• The image includes c3270 - so you have the option to attach to it via a normal ssh console and run c3270 docker exec -it vm370 /bin/bash

Other hints

• To attach to the container: docker exec -it vm370 /bin/bash - you could then run c3270

• To stop/start the container: docker start vm370 / docker stop vm370

• copy files with docker cp

The source is here:

https://github.com/adesutherland/vm-370

Notes:

• I have master, develop (and from time to time feature) branches - so switch to develop for the latest and greatest, etc.

• There is the Dockerfile, and a build.sh script (uses HercControl)

• in .github/workflows are the action scripts that automatically cause the image to be build/tested. These look so simple but are are very irritating to debug!

• A tag causes a release that pushes an image to dockerhub and makes a zip file with the DASD files in the release page.

• At the moment tied to the DASD files from the excellent six pack - when my build scripts starts adding updates (e,g, GCCLIB, fullscreen stuff, BREXX updates whatever) automatically, I am hoping Dave and community will be inspired to build scripts to automate the build from a basic baseline (if that makes sense).