Inter container communication in Kubernetes multi container Pod The Next CEO of Stack OverflowKubernetes setup for docker container - kubectl get minions failingerror: couldn't read version from server: Get http://localhost:8080/api: dial tcp 127.0.0.1:8080: connection refusedCannot access apiserver on kubernetes v1.2.0How to map one single file into kubernetes pod using hostPath?Can't Connect to Kubernetes Service from Inside Service Pod?Kubernetes failed to discover supported resources: getsockopt: connection refusedGKE accessing serviceKubernetes pod access without mentioning container portHow to run a docker image on kubernetes that accepts command line arguments?Envoy Pod to Pod communication within a Service in K8
MessageLevel in QGIS3
Would a completely good Muggle be able to use a wand?
If Nick Fury and Coulson already knew about aliens (Kree and Skrull) why did they wait until Thor's appearance to start making weapons?
What exact does MIB represent in SNMP? How is it different from OID?
What does convergence in distribution "in the Gromov–Hausdorff" sense mean?
To not tell, not take, and not want
What can we do to stop prior company from asking us questions?
Why didn't Khan get resurrected in the Genesis Explosion?
Is it ever safe to open a suspicious html file (e.g. email attachment)?
Preparing Indesign booklet with .psd graphics for print
How powerful is the invisibility granted by the Gloom Stalker ranger's Umbral Sight feature?
What connection does MS Office have to Netscape Navigator?
How to solve a differential equation with a term to a power?
Rotate a column
Is 'diverse range' a pleonastic phrase?
Contours of a clandestine nature
Is it professional to write unrelated content in an almost-empty email?
What is "(CFMCC)" on an ILS approach chart?
Why does standard notation not preserve intervals (visually)
What's the best way to handle refactoring a big file?
What was the first Unix version to run on a microcomputer?
Why am I allowed to create multiple unique pointers from a single object?
What benefits would be gained by using human laborers instead of drones in deep sea mining?
How does the mv command work with external drives?
Inter container communication in Kubernetes multi container Pod
The Next CEO of Stack OverflowKubernetes setup for docker container - kubectl get minions failingerror: couldn't read version from server: Get http://localhost:8080/api: dial tcp 127.0.0.1:8080: connection refusedCannot access apiserver on kubernetes v1.2.0How to map one single file into kubernetes pod using hostPath?Can't Connect to Kubernetes Service from Inside Service Pod?Kubernetes failed to discover supported resources: getsockopt: connection refusedGKE accessing serviceKubernetes pod access without mentioning container portHow to run a docker image on kubernetes that accepts command line arguments?Envoy Pod to Pod communication within a Service in K8
I have a pod with 3 containers A, B, and C. I would like to access service in Container A and B from C. Neither localhost:<port> is working nor the 127.0.0.1.
my yaml
apiVersion: "v1"
kind: Pod
metadata:
name: web3
labels:
name: web
app: demo
spec:
containers:
- name: client
image: ubuntu
command: ['cat']
tty: true
- name: apache1
image: nimmis/apache-php5
ports:
- containerPort: 8080
name: apacheport1
protocol: TCP
- name: apache2
image: nimmis/apache-php5
command: ['cat']
tty: true
ports:
- containerPort: 8088
name: apacheport2
protocol: TCP
what I am doing
kubectl apply -f example.yaml
kubectl exec -it web3 -c client bash
and then try to reach other 2 services
root@web3:/# curl http://localhost:8080
curl: (7) Failed to connect to localhost port 8080: Connection refused
root@web3:/# curl http://localhost:8088
curl: (7) Failed to connect to localhost port 8088: Connection refused
root@web3:/# curl http://localhost:80
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<!--
Modified from the Debian original for Ubuntu
Questions
How to make the first 2 curl work. (I do not want to use the service since my use case is only for testing purpose)
Why there is an open port 80 when I haven't exposed the port.
kubernetes kubernetes-pod asked Mar 8 at 14:30
Ram KamathRam Kamath
651416
add a comment |
I have a pod with 3 containers A, B, and C. I would like to access service in Container A and B from C. Neither localhost:<port> is working nor the 127.0.0.1.
my yaml
apiVersion: "v1"
kind: Pod
metadata:
name: web3
labels:
name: web
app: demo
spec:
containers:
- name: client
image: ubuntu
command: ['cat']
tty: true
- name: apache1
image: nimmis/apache-php5
ports:
- containerPort: 8080
name: apacheport1
protocol: TCP
- name: apache2
image: nimmis/apache-php5
command: ['cat']
tty: true
ports:
- containerPort: 8088
name: apacheport2
protocol: TCP
what I am doing
kubectl apply -f example.yaml
kubectl exec -it web3 -c client bash
and then try to reach other 2 services
root@web3:/# curl http://localhost:8080
curl: (7) Failed to connect to localhost port 8080: Connection refused
root@web3:/# curl http://localhost:8088
curl: (7) Failed to connect to localhost port 8088: Connection refused
root@web3:/# curl http://localhost:80
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<!--
Modified from the Debian original for Ubuntu
Questions
How to make the first 2 curl work. (I do not want to use the service since my use case is only for testing purpose)
Why there is an open port 80 when I haven't exposed the port.
kubernetes kubernetes-pod asked Mar 8 at 14:30
Ram KamathRam Kamath
651416
what's the exposed port inside the nimmis/apache-php5 image?
– fiunchinho
Mar 8 at 16:44
80 and 443 ports are open in Apache container
– Ram Kamath
Mar 8 at 17:15
add a comment |
I have a pod with 3 containers A, B, and C. I would like to access service in Container A and B from C. Neither localhost:<port> is working nor the 127.0.0.1.
my yaml
apiVersion: "v1"
kind: Pod
metadata:
name: web3
labels:
name: web
app: demo
spec:
containers:
- name: client
image: ubuntu
command: ['cat']
tty: true
- name: apache1
image: nimmis/apache-php5
ports:
- containerPort: 8080
name: apacheport1
protocol: TCP
- name: apache2
image: nimmis/apache-php5
command: ['cat']
tty: true
ports:
- containerPort: 8088
name: apacheport2
protocol: TCP
what I am doing
kubectl apply -f example.yaml
kubectl exec -it web3 -c client bash
and then try to reach other 2 services
root@web3:/# curl http://localhost:8080
curl: (7) Failed to connect to localhost port 8080: Connection refused
root@web3:/# curl http://localhost:8088
curl: (7) Failed to connect to localhost port 8088: Connection refused
root@web3:/# curl http://localhost:80
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<!--
Modified from the Debian original for Ubuntu
Questions
How to make the first 2 curl work. (I do not want to use the service since my use case is only for testing purpose)
Why there is an open port 80 when I haven't exposed the port.
kubernetes kubernetes-pod asked Mar 8 at 14:30
Ram KamathRam Kamath
651416
I have a pod with 3 containers A, B, and C. I would like to access service in Container A and B from C. Neither localhost:<port> is working nor the 127.0.0.1.
my yaml
apiVersion: "v1"
kind: Pod
metadata:
name: web3
labels:
name: web
app: demo
spec:
containers:
- name: client
image: ubuntu
command: ['cat']
tty: true
- name: apache1
image: nimmis/apache-php5
ports:
- containerPort: 8080
name: apacheport1
protocol: TCP
- name: apache2
image: nimmis/apache-php5
command: ['cat']
tty: true
ports:
- containerPort: 8088
name: apacheport2
protocol: TCP
what I am doing
kubectl apply -f example.yaml
kubectl exec -it web3 -c client bash
and then try to reach other 2 services
root@web3:/# curl http://localhost:8080
curl: (7) Failed to connect to localhost port 8080: Connection refused
root@web3:/# curl http://localhost:8088
curl: (7) Failed to connect to localhost port 8088: Connection refused
root@web3:/# curl http://localhost:80
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<!--
Modified from the Debian original for Ubuntu
Questions
How to make the first 2 curl work. (I do not want to use the service since my use case is only for testing purpose)
Why there is an open port 80 when I haven't exposed the port.
kubernetes kubernetes-pod kubernetes kubernetes-pod asked Mar 8 at 14:30
Ram KamathRam Kamath
651416
asked Mar 8 at 14:30
Ram KamathRam Kamath
651416
asked Mar 8 at 14:30
Ram KamathRam Kamath
651416
asked Mar 8 at 14:30
Ram KamathRam Kamath
651416
asked Mar 8 at 14:30
Ram KamathRam Kamath
651416
651416
what's the exposed port inside the nimmis/apache-php5 image?
– fiunchinho
Mar 8 at 16:44
80 and 443 ports are open in Apache container
– Ram Kamath
Mar 8 at 17:15
add a comment |
what's the exposed port inside the nimmis/apache-php5 image?
– fiunchinho
Mar 8 at 16:44
80 and 443 ports are open in Apache container
– Ram Kamath
Mar 8 at 17:15
what's the exposed port inside the nimmis/apache-php5 image?
– fiunchinho
Mar 8 at 16:44
what's the exposed port inside the nimmis/apache-php5 image?
– fiunchinho
Mar 8 at 16:44
80 and 443 ports are open in Apache container
– Ram Kamath
Mar 8 at 17:15
80 and 443 ports are open in Apache container
– Ram Kamath
Mar 8 at 17:15
add a comment |
1 Answer
1
active
oldest
votes
The point is that with nimmis/apache-php5 Apache is listening on port 80.
So, it's port 80 which is exposed.
Through containerPort: <P> you are not saying to expose container's port 80 to <P>, but rather exposing port <P> itself. Also, as written in the docs, Not specifying a port here DOES NOT prevent that port from being exposed..
I did not find a way to map an internal container port to a different port in the pod. However, you may map the internal container port to a host port through field hostPort.
apiVersion: "v1"
kind: Pod
metadata:
name: web3
labels:
name: web
app: demo
spec:
containers:
- name: client
image: ubuntu
command: ['cat']
tty: true
- name: apache1
image: nimmis/apache-php5
ports:
- containerPort: 80
name: apacheport1
hostPort: 8002
protocol: TCP
- name: apache2
image: nimmis/apache-php5
command: ['cat']
tty: true
ports:
- containerPort: 80
hostPort: 8001
name: apacheport2
protocol: TCP
Then you get the IP of the node, e.g., on Minikube
$ minikube ip # e.g., 192.168.97.100
and check that, from client, you can access the Apache services:
$ kubectl exec -it web3 -c client bash
# apt-get update && apt-get install curl
# curl 192.168.99.100:8002
answered Mar 8 at 17:33
metaphorimetaphori
1,52311127
There is no way to replicate -p hostPort:containerPort behavior of docker in a Pod ?
– Ram Kamath
Mar 8 at 17:36
An option would be to usehostPortto expose thecontainerPort: 80to a port of the host. Then, you wouldcurlathostIP:hostPort.
– metaphori
Mar 8 at 21:20
Thanks a lot for your time. I tried that option but couldn’t create a pod when I had host port mapping enabled. Do you have a minimal working example handy somewhere? I also read somewhere that the hostPort actually refers to the actual kubernetes node.
– Ram Kamath
Mar 8 at 21:23
Yes, it maps a port on the cluster node running the pod. I've extended the answer with an example. I just would like to remark that exposing stuff is done through services.
– metaphori
Mar 8 at 21:33
Thanks, that clarifies my question and I have better understanding now towards the solution.
– Ram Kamath
Mar 8 at 21:51
add a comment |
Your Answer
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55065273%2finter-container-communication-in-kubernetes-multi-container-pod%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
The point is that with nimmis/apache-php5 Apache is listening on port 80.
So, it's port 80 which is exposed.
Through containerPort: <P> you are not saying to expose container's port 80 to <P>, but rather exposing port <P> itself. Also, as written in the docs, Not specifying a port here DOES NOT prevent that port from being exposed..
I did not find a way to map an internal container port to a different port in the pod. However, you may map the internal container port to a host port through field hostPort.
apiVersion: "v1"
kind: Pod
metadata:
name: web3
labels:
name: web
app: demo
spec:
containers:
- name: client
image: ubuntu
command: ['cat']
tty: true
- name: apache1
image: nimmis/apache-php5
ports:
- containerPort: 80
name: apacheport1
hostPort: 8002
protocol: TCP
- name: apache2
image: nimmis/apache-php5
command: ['cat']
tty: true
ports:
- containerPort: 80
hostPort: 8001
name: apacheport2
protocol: TCP
Then you get the IP of the node, e.g., on Minikube
$ minikube ip # e.g., 192.168.97.100
and check that, from client, you can access the Apache services:
$ kubectl exec -it web3 -c client bash
# apt-get update && apt-get install curl
# curl 192.168.99.100:8002
answered Mar 8 at 17:33
metaphorimetaphori
1,52311127
There is no way to replicate -p hostPort:containerPort behavior of docker in a Pod ?
– Ram Kamath
Mar 8 at 17:36
An option would be to usehostPortto expose thecontainerPort: 80to a port of the host. Then, you wouldcurlathostIP:hostPort.
– metaphori
Mar 8 at 21:20
Thanks a lot for your time. I tried that option but couldn’t create a pod when I had host port mapping enabled. Do you have a minimal working example handy somewhere? I also read somewhere that the hostPort actually refers to the actual kubernetes node.
– Ram Kamath
Mar 8 at 21:23
Yes, it maps a port on the cluster node running the pod. I've extended the answer with an example. I just would like to remark that exposing stuff is done through services.
– metaphori
Mar 8 at 21:33
Thanks, that clarifies my question and I have better understanding now towards the solution.
– Ram Kamath
Mar 8 at 21:51
add a comment |
The point is that with nimmis/apache-php5 Apache is listening on port 80.
So, it's port 80 which is exposed.
Through containerPort: <P> you are not saying to expose container's port 80 to <P>, but rather exposing port <P> itself. Also, as written in the docs, Not specifying a port here DOES NOT prevent that port from being exposed..
I did not find a way to map an internal container port to a different port in the pod. However, you may map the internal container port to a host port through field hostPort.
apiVersion: "v1"
kind: Pod
metadata:
name: web3
labels:
name: web
app: demo
spec:
containers:
- name: client
image: ubuntu
command: ['cat']
tty: true
- name: apache1
image: nimmis/apache-php5
ports:
- containerPort: 80
name: apacheport1
hostPort: 8002
protocol: TCP
- name: apache2
image: nimmis/apache-php5
command: ['cat']
tty: true
ports:
- containerPort: 80
hostPort: 8001
name: apacheport2
protocol: TCP
Then you get the IP of the node, e.g., on Minikube
$ minikube ip # e.g., 192.168.97.100
and check that, from client, you can access the Apache services:
$ kubectl exec -it web3 -c client bash
# apt-get update && apt-get install curl
# curl 192.168.99.100:8002
answered Mar 8 at 17:33
metaphorimetaphori
1,52311127
There is no way to replicate -p hostPort:containerPort behavior of docker in a Pod ?
– Ram Kamath
Mar 8 at 17:36
An option would be to usehostPortto expose thecontainerPort: 80to a port of the host. Then, you wouldcurlathostIP:hostPort.
– metaphori
Mar 8 at 21:20
Thanks a lot for your time. I tried that option but couldn’t create a pod when I had host port mapping enabled. Do you have a minimal working example handy somewhere? I also read somewhere that the hostPort actually refers to the actual kubernetes node.
– Ram Kamath
Mar 8 at 21:23
Yes, it maps a port on the cluster node running the pod. I've extended the answer with an example. I just would like to remark that exposing stuff is done through services.
– metaphori
Mar 8 at 21:33
Thanks, that clarifies my question and I have better understanding now towards the solution.
– Ram Kamath
Mar 8 at 21:51
add a comment |
The point is that with nimmis/apache-php5 Apache is listening on port 80.
So, it's port 80 which is exposed.
Through containerPort: <P> you are not saying to expose container's port 80 to <P>, but rather exposing port <P> itself. Also, as written in the docs, Not specifying a port here DOES NOT prevent that port from being exposed..
I did not find a way to map an internal container port to a different port in the pod. However, you may map the internal container port to a host port through field hostPort.
apiVersion: "v1"
kind: Pod
metadata:
name: web3
labels:
name: web
app: demo
spec:
containers:
- name: client
image: ubuntu
command: ['cat']
tty: true
- name: apache1
image: nimmis/apache-php5
ports:
- containerPort: 80
name: apacheport1
hostPort: 8002
protocol: TCP
- name: apache2
image: nimmis/apache-php5
command: ['cat']
tty: true
ports:
- containerPort: 80
hostPort: 8001
name: apacheport2
protocol: TCP
Then you get the IP of the node, e.g., on Minikube
$ minikube ip # e.g., 192.168.97.100
and check that, from client, you can access the Apache services:
$ kubectl exec -it web3 -c client bash
# apt-get update && apt-get install curl
# curl 192.168.99.100:8002
answered Mar 8 at 17:33
metaphorimetaphori
1,52311127
The point is that with nimmis/apache-php5 Apache is listening on port 80.
So, it's port 80 which is exposed.
Through containerPort: <P> you are not saying to expose container's port 80 to <P>, but rather exposing port <P> itself. Also, as written in the docs, Not specifying a port here DOES NOT prevent that port from being exposed..
I did not find a way to map an internal container port to a different port in the pod. However, you may map the internal container port to a host port through field hostPort.
apiVersion: "v1"
kind: Pod
metadata:
name: web3
labels:
name: web
app: demo
spec:
containers:
- name: client
image: ubuntu
command: ['cat']
tty: true
- name: apache1
image: nimmis/apache-php5
ports:
- containerPort: 80
name: apacheport1
hostPort: 8002
protocol: TCP
- name: apache2
image: nimmis/apache-php5
command: ['cat']
tty: true
ports:
- containerPort: 80
hostPort: 8001
name: apacheport2
protocol: TCP
Then you get the IP of the node, e.g., on Minikube
$ minikube ip # e.g., 192.168.97.100
and check that, from client, you can access the Apache services:
$ kubectl exec -it web3 -c client bash
# apt-get update && apt-get install curl
# curl 192.168.99.100:8002
answered Mar 8 at 17:33
metaphorimetaphori
1,52311127
edited Mar 8 at 21:31
answered Mar 8 at 17:33
metaphorimetaphori
1,52311127
answered Mar 8 at 17:33
metaphorimetaphori
1,52311127
answered Mar 8 at 17:33
metaphorimetaphori
1,52311127
1,52311127
There is no way to replicate -p hostPort:containerPort behavior of docker in a Pod ?
– Ram Kamath
Mar 8 at 17:36
An option would be to usehostPortto expose thecontainerPort: 80to a port of the host. Then, you wouldcurlathostIP:hostPort.
– metaphori
Mar 8 at 21:20
Thanks a lot for your time. I tried that option but couldn’t create a pod when I had host port mapping enabled. Do you have a minimal working example handy somewhere? I also read somewhere that the hostPort actually refers to the actual kubernetes node.
– Ram Kamath
Mar 8 at 21:23
Yes, it maps a port on the cluster node running the pod. I've extended the answer with an example. I just would like to remark that exposing stuff is done through services.
– metaphori
Mar 8 at 21:33
Thanks, that clarifies my question and I have better understanding now towards the solution.
– Ram Kamath
Mar 8 at 21:51
add a comment |
There is no way to replicate -p hostPort:containerPort behavior of docker in a Pod ?
– Ram Kamath
Mar 8 at 17:36
An option would be to usehostPortto expose thecontainerPort: 80to a port of the host. Then, you wouldcurlathostIP:hostPort.
– metaphori
Mar 8 at 21:20
Thanks a lot for your time. I tried that option but couldn’t create a pod when I had host port mapping enabled. Do you have a minimal working example handy somewhere? I also read somewhere that the hostPort actually refers to the actual kubernetes node.
– Ram Kamath
Mar 8 at 21:23
Yes, it maps a port on the cluster node running the pod. I've extended the answer with an example. I just would like to remark that exposing stuff is done through services.
– metaphori
Mar 8 at 21:33
Thanks, that clarifies my question and I have better understanding now towards the solution.
– Ram Kamath
Mar 8 at 21:51
There is no way to replicate -p hostPort:containerPort behavior of docker in a Pod ?
– Ram Kamath
Mar 8 at 17:36
There is no way to replicate -p hostPort:containerPort behavior of docker in a Pod ?
– Ram Kamath
Mar 8 at 17:36
An option would be to use
hostPort to expose the containerPort: 80 to a port of the host. Then, you would curl at hostIP:hostPort.– metaphori
Mar 8 at 21:20
An option would be to use
hostPort to expose the containerPort: 80 to a port of the host. Then, you would curl at hostIP:hostPort.– metaphori
Mar 8 at 21:20
Thanks a lot for your time. I tried that option but couldn’t create a pod when I had host port mapping enabled. Do you have a minimal working example handy somewhere? I also read somewhere that the hostPort actually refers to the actual kubernetes node.
– Ram Kamath
Mar 8 at 21:23
Thanks a lot for your time. I tried that option but couldn’t create a pod when I had host port mapping enabled. Do you have a minimal working example handy somewhere? I also read somewhere that the hostPort actually refers to the actual kubernetes node.
– Ram Kamath
Mar 8 at 21:23
Yes, it maps a port on the cluster node running the pod. I've extended the answer with an example. I just would like to remark that exposing stuff is done through services.
– metaphori
Mar 8 at 21:33
Yes, it maps a port on the cluster node running the pod. I've extended the answer with an example. I just would like to remark that exposing stuff is done through services.
– metaphori
Mar 8 at 21:33
Thanks, that clarifies my question and I have better understanding now towards the solution.
– Ram Kamath
Mar 8 at 21:51
Thanks, that clarifies my question and I have better understanding now towards the solution.
– Ram Kamath
Mar 8 at 21:51
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55065273%2finter-container-communication-in-kubernetes-multi-container-pod%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
what's the exposed port inside the nimmis/apache-php5 image?
– fiunchinho
Mar 8 at 16:44
80 and 443 ports are open in Apache container
– Ram Kamath
Mar 8 at 17:15