They mostly just want to punt the problem of persistent data to someone
else and make it their problem to preserve 'architectural purity' or some
such.
On Fri, Aug 4, 2017 at 11:23 AM, Neale Ferguson
wrote:
> I am proposing the certificate(s) only. All other items are
I am proposing the certificate(s) only. All other items are catered for by the
other mechanisms of which you speak. The --ip and --hostname options take care
of the network configuration. I would be interested in what the anti-VOLUMEites
propose for things like persistent data.
On 8/4/17,
Yes, and according to 'the community' you should not use VOLUME for things
like passing a hostname, ip address, or any other configuration option
which can conceivably be passed via a variable or by a configuration
service.
There is actually a part of the community that feels like VOLUME is an
That is why VOLUME is there so that your persistent or customized data is
not part of the image.
On 8/4/17, 10:18 AM, "Linux on 390 Port on behalf of Robert J Brenneman"
wrote:
>best practice with docker is to keep a docker image
best practice with docker is to keep a docker image absolutely generic so
that it can be deployed to dev/test/production without any changes. Any
personalization that needs to be done to make the docker container do it's
job should be either
a) passed to the docker container at startup through
: Michael MacIsaac <mike99...@gmail.com>
Reply-To: Linux on 390 Port <LINUX-390@VM.MARIST.EDU>
To: LINUX-390@VM.MARIST.EDU
Subject: Docker question
Hello list,
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 Apac
Neale,
Thanks for the quick reply. That's great.
-Mike
On Fri, Aug 4, 2017 at 9:42 AM, Neale Ferguson wrote:
> 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
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
Hello list,
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