Re: Have a working storage under VM/370
¿ªÔÆÌåÓýwell, we can try to support running in Docker (a bit).So please tell me you are persisting the container after you stop it, to a new image. Otherwise, you will start a new container from the old image, and that will contain the unchanged disk images. You need to do something like (showing you with my netrexx s/390x image): ? ?test git:(master) ? docker run -it rvjansen/netrexx WARNING: The requested image's platform (linux/s390x) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested root@6ffb982a8a2d:~# ls root@6ffb982a8a2d:~# nrc Usage: /bin/NetRexxC.sh [-run] [other options] filename *** WARNING *** Ambiguous z/Architecture detection! ? ? ? ? ? ? ? ? oldest detected generation is system-z, g6-ec12, ldisp_fast, extimm, pcrel_load/store, cmpb, cond_load/store, interlocked_update, txm NetRexx portable processor 4.05-alpha build 196-20221110-1459 Copyright (c) RexxLA, 2011,2022. ? All rights reserved. Parts Copyright (c) IBM Corporation, 1995,2008. Arguments are: in_file_specification... [-option]... Use "--help" to show all options root@6ffb982a8a2d:~# exit exit Never mind the warnings, did not see them before but that is not the point here. What is the point, is that after you exit, you need to persist the container image with 'docker commit' ? ?test git:(master) ? docker commit 6ffb982a8a2d sha256:929e7bcda67826e4011cbf3c636c612eb8339205327f14072ed7d3cb14051c89 And the, you can rename the persisted container image for use the next time: ? ?test git:(master) ? docker tag 929e7bcda67826e4011cbf3c636c612eb8339205327f14072ed7d3cb14051c89 rvjansen/netrexx The greater good here is that if you messed up something, you can just choose not to persist the image and restart with an unchanged one - no real need for shadow files in a container. Let us know if that was the problem! best regards, Ren¨¦ Jansen.
|
