# docker kubernetes

**URL:** <https://discuss.kubernetes.io/t/docker-kubernetes/5066>\
**Category:** General Discussions\
**Created:** [February 26, 2019, 12:25pm UTC](https://discuss.kubernetes.io/t/docker-kubernetes/5066 "2019-02-26T12:25:06Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![linuly](https://avatars.discourse-cdn.com/v4/letter/l/d9b06d/32.png) [@linuly](https://discuss.kubernetes.io/u/linuly)\
**Post date:** [February 26, 2019, 12:25pm UTC](https://discuss.kubernetes.io/t/docker-kubernetes/5066/1 "2019-02-26T12:25:06Z")

</div>

hi,  
in a pod i have 2 docker containers-\>a container run nginx and other run httpd.  
i understood that the pod is seen by OS as a process.  
with ps aux can i see the processes for nginx and httpd as well?  
inside the kubernetes does not run other OS on top of OS on physical host.right?  
tnx

---

<div class="post-metadata">

**Author:** ![rata](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.kubernetes.io/rata/32/18244_2.png) [@rata](https://discuss.kubernetes.io/u/rata)\
**Post date:** [February 26, 2019, 5:34pm UTC](https://discuss.kubernetes.io/t/docker-kubernetes/5066/2 "2019-02-26T17:34:13Z")

</div>

Each container is a different process (even if they are on the same pod).

You won’t be able to see from nginx process httpd running PS faux. There is experimental support for that.

And right, the container just runs a process, does not boot another OS.

---

<div class="post-metadata">

**Author:** ![linuly](https://avatars.discourse-cdn.com/v4/letter/l/d9b06d/32.png) [@linuly](https://discuss.kubernetes.io/u/linuly)\
**Post date:** [February 27, 2019, 8:18am UTC](https://discuss.kubernetes.io/t/docker-kubernetes/5066/3 "2019-02-27T08:18:01Z")

</div>

we have -kubernete process and the 2 docker container processes.right?  
the kubernete process is used in kubernete cluster-load balancing of resources.right?

---

<div class="post-metadata">

**Author:** ![rata](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.kubernetes.io/rata/32/18244_2.png) [@rata](https://discuss.kubernetes.io/u/rata)\
**Post date:** [February 27, 2019, 12:13pm UTC](https://discuss.kubernetes.io/t/docker-kubernetes/5066/4 "2019-02-27T12:13:22Z")

</div>

It depends if you want to start automatically if it’s stopped or not. You can try all these things, too 🙂

---

<div class="post-metadata">

**Author:** ![linuly](https://avatars.discourse-cdn.com/v4/letter/l/d9b06d/32.png) [@linuly](https://discuss.kubernetes.io/u/linuly)\
**Post date:** [February 27, 2019, 2:35pm UTC](https://discuss.kubernetes.io/t/docker-kubernetes/5066/5 "2019-02-27T14:35:57Z")

</div>

hi,  
somehow the kubernete process is the parent process to nginx and http processes?

---

<div class="post-metadata">

**Author:** ![rata](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.kubernetes.io/rata/32/18244_2.png) [@rata](https://discuss.kubernetes.io/u/rata)\
**Post date:** [February 27, 2019, 3:46pm UTC](https://discuss.kubernetes.io/t/docker-kubernetes/5066/6 "2019-02-27T15:46:29Z")

</div>

What do you mean with the kubernetes process?

It’s just a container (probably docker container). Nothing different there. Feel free to read more docs and come back if you have any other questions 🙂

---

<div class="post-metadata">

**Author:** ![linuly](https://avatars.discourse-cdn.com/v4/letter/l/d9b06d/32.png) [@linuly](https://discuss.kubernetes.io/u/linuly)\
**Post date:** [February 28, 2019, 7:27am UTC](https://discuss.kubernetes.io/t/docker-kubernetes/5066/7 "2019-02-28T07:27:33Z")

</div>

when a pod is created there will be a process that run this pod.right?

---

<div class="post-metadata">

**Author:** ![mrbobbytables](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.kubernetes.io/mrbobbytables/32/7_2.png) [@mrbobbytables](https://discuss.kubernetes.io/u/mrbobbytables)\
**Post date:** [February 28, 2019, 12:41pm UTC](https://discuss.kubernetes.io/t/docker-kubernetes/5066/8 "2019-02-28T12:41:37Z")

</div>

Kubelet, the kubernetes node agent manages the pods on the host. However it is not a process that starts within and manages your containers. Functionally, containers will start the same way as if they were run in docker with the exception they share the same network identity.

---

<div class="post-metadata">

**Author:** ![linuly](https://avatars.discourse-cdn.com/v4/letter/l/d9b06d/32.png) [@linuly](https://discuss.kubernetes.io/u/linuly)\
**Post date:** [February 28, 2019, 2:37pm UTC](https://discuss.kubernetes.io/t/docker-kubernetes/5066/9 "2019-02-28T14:37:24Z")

</div>

if the host where this pod runs fails then automatically the pod fails over to other host.i think the kubernetes cluster knows about the pod structure and thus the docker containers inside the pod failsover.  
right?

---

<div class="post-metadata">

**Author:** ![mrbobbytables](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.kubernetes.io/mrbobbytables/32/7_2.png) [@mrbobbytables](https://discuss.kubernetes.io/u/mrbobbytables)\
**Post date:** [February 28, 2019, 2:44pm UTC](https://discuss.kubernetes.io/t/docker-kubernetes/5066/10 "2019-02-28T14:44:49Z")

</div>

Correct. Kubernetes will try and place the workloads on other hosts.
