This container_scripts directory should be placed as a directory
immediately above your mvs3.8j directory (ie: above the one that has
directories dasd, shadow etc).

Edit the Dockerfile to globally change my mvs38j directory name
(tk4-minus) to whatever your directory name is called.

Edit the container_environment.conf and do the same, also
in there check the directory layout variables match what 
you use in your hercules config file.

Copy the Dockerfile up one directory level, to immediately
above the container_scripts and your mvs3.8j directory.

Do a docker/podman build and you should have a working container.
Note: manually clean up the temporary image layers from the build left behind.

----- IMPORTANT TK4- HERCULES CONF FILE NOTES BELOW -----
As shipped the startup script and healthcheck script are for a TK4- based system
with consoles re-defined as the below, if your setup is different you may need to
adjust them (TK3 from memory does not use 01F and 009 is the hardcopy so one less
screen session). The TK4-/TK4ROB console setup below allows the TSO interfaces SPY and
IMON option O to actually display whats on the consoles [they need a 3270 screen buffer]
and you need to be able to see the consoles from TSO (as the real consoles are
hidden away within the container so TSO is the main interface to them).

# 3270 consoles on 010 and 011
# 009 is used by hercules as a console interface
# 01F is a telnet hardcopy interface
0009 3215-C
0010 3270 CONS
0011 3270 CONS
001F 3215

If you are not getting any data in the Q SLOG cmmand you should
use the console command "V SYSLOG,HARDCPY,STCMDS" to fix that;
although syslog is always one screen buffer behind what is on 
the consoles.
