I think you could define on each container in the pod a volume mount of /var/run/apache/ and have them point to the same emptydir, and then have apache configured to use /var/run/apache/apache.sock, and then the other container should see that socket appear once apache starts.
On Fri, Mar 11, 2016 at 3:16 PM, Braswell, Stephen <[email protected]> wrote: > Thanks for the information, Clayton. I’m not sure how to implement that but > it gives me a starting point for toying around. I may have more questions > later. > > > -Stephen > >> On Mar 11, 2016, at 2:31 PM, Clayton Coleman <[email protected]> wrote: >> >> For anything that pods make easy today (sharing filesystems, IPC, >> network namespace, or shared memory) you can use a pod. You can also >> have a container share itself with another container over a filesystem >> in order to provide a binary the main container can run. That might >> be inefficient though, and isn't cleanly decoupled. >> >> For apache sockets I would use a shared volume and have apache listen >> inside the shared volume (for your example). >> >> On Fri, Mar 11, 2016 at 2:28 PM, Braswell, Stephen <[email protected]> wrote: >>> Hi everyone, >>> >>> In OpenShift v2, there was the concept of an add-on cartridge to add >>> software to an existing gear. Is there a similar process for doing >>> something similar in v3? >>> >>> Here is an example of a situation: >>> >>> I have software I need to package to provide to my customers for our >>> on-premise v3 installation. The software needs to be installed in the same >>> container as other software (e.g. Apache) because it has an Apache module >>> or it only listens on sockets instead of TCP. Should I be providing a >>> template that contains both or is there a way to add a layer on top of an >>> existing running image? >>> >>> >>> Thanks, >>> >>> -Stephen >>> >>> _______________________________________________ >>> users mailing list >>> [email protected] >>> http://lists.openshift.redhat.com/openshiftmm/listinfo/users > _______________________________________________ users mailing list [email protected] http://lists.openshift.redhat.com/openshiftmm/listinfo/users
