Yes, I have seen such examples. The volumes-from works nicely for this use case (just Docker) in my opinion. However, I was not aware it could access any volume on the system. That seems like a huge potential problem.
I think the next best thing is the current previously referenced solution. Thank much for the replies, Carl On Mon, Mar 21, 2016 at 10:41 PM, Clayton Coleman <[email protected]> wrote: > Generally that would be an image that on startup copies its config > into a volume, which all the other containers in the pod can then see. > We do not support the volumes-from syntax because it assumes generic > access to other containers on the system, and is not bounded to the > lifetime of a pod. Future releases of Kubernetes may add the idea of > the "init container" which is allowed to run first (and fail first). > > On Mon, Mar 21, 2016 at 10:26 PM, Carl Mosca <[email protected]> wrote: > > A little more background...I have a legacy app which combines > technologies. > > The need is to use some application and configuration files which are in > one > > image in multiple containers. I would like to create template which > handles > > all of this. > > > > Currently, there are multiple images which have a great deal of duplicate > > files which I would like to eliminated. > > > > I would rather not use (an) empty volume(s) to which I would have to copy > > these files upon startup. > > > > On Mon, Mar 21, 2016 at 10:12 PM, Clayton Coleman <[email protected]> > > wrote: > >> > >> The EmptyDir volume type handles that - you create a volume in your > >> pod template and then specify where it should be mounted into each > >> container. The "oc volume" command can help add and remove volumes > >> (see the examples) from deployment configs or replication controllers. > >> > >> > On Mar 21, 2016, at 10:11 PM, Carl Mosca <[email protected]> > wrote: > >> > > >> > Is it possible to use --volumes-from or something comparable to share > >> > non-persistent volumes with containers within a pod? > >> > > >> > TIA, > >> > Carl > >> > > >> > Carl J. Mosca > >> > _______________________________________________ > >> > dev mailing list > >> > [email protected] > >> > http://lists.openshift.redhat.com/openshiftmm/listinfo/dev > > > > > > > > > > -- > > Carl J. Mosca > -- Carl J. Mosca
_______________________________________________ dev mailing list [email protected] http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
