The `--volumes-from` bit is not at all what Kubernetes does. Rather, volumes are a first-class construct that live disassociated from any containers, and are then bindmounted into a subset of containers in the pod. Any `VOLUME`s declared in a given image are not shared implicitly as the above commands would imply as well.
A pod also now has the concept of "Init Containers" which provides containers which should be run first, so there are now some ordering constraints which are difficult to express in terms of just a few docker commands. - Euan On Tuesday, October 4, 2016 at 7:41:17 PM UTC-7, Anthony Alba wrote: > > Aside from the orchestration, is a pod equivalent to a set of containers > with shared IPC, net, PID, and volumes? > > I.e when Kubernetes creates a pod is it doing, behind the scenes, the > equivalent of > > docker run --name first app1 > docker run --net container:first --ipc container:first --pid > container:first --volumes-from first app2 > docker run --net container:first --ipc container:first --pid > container:first --volumes-from first app3 > > where <container:id> is obtained from first, or is there more to pods than > this? > > Thanks. > > -- You received this message because you are subscribed to the Google Groups "Kubernetes user discussion and Q&A" group. To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-users+unsubscr...@googlegroups.com. To post to this group, send email to kubernetes-users@googlegroups.com. Visit this group at https://groups.google.com/group/kubernetes-users. For more options, visit https://groups.google.com/d/optout.
