A couple of options. First the certificates: build the container with a VOLUME statement that you will then use the -v option on the docker run command to mount a unique file or directory on. That would contain your certificate although isn’t it possible to put all the certs in /etc/pki/…
Use --ip option to assign a fixed IP to the container – see https://stackoverflow.com/questions/27937185/assign-static-ip-to-docker-container Alternatively you could use something like openShift that allows you to configure this including allowing you to assign publicly accessible IP addresses to the container (openShift runs haproxy). For a description of building and running things on openShift Origin under Linux on Z see: http://download.sinenomine.net/clefos/epel7/Getting_Started_with_OpenShift_on_z.pdf Neale On 8/4/17, 9:32 AM, "Linux on 390 Port on behalf of Michael MacIsaac" <LINUX-390@VM.MARIST.EDU<mailto:LINUX-390@VM.MARIST.EDU> on behalf of mike99...@gmail.com<mailto:mike99...@gmail.com>> wrote: I still don't grok Docker. Let's say I want to create a Docker image of a zLinux system. Let's say this system runs Apache and needs a certificate to enable https. Let's say I want to run this image on multiple LPARs. So each system will need a unique host name and thus a unique certificate, right? ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/
