Just to be clear, you need to tell the application to bind to a different
port. You can't just change the port numbers in the yaml file.
On Thu, Mar 2, 2017 at 8:03 PM Rodrigo Campos wrote:
> On Thu, Mar 02, 2017 at 07:38:38PM -0800, Montassar Dridi wrote:
> > I tried different port, still getti
On Thu, Mar 02, 2017 at 07:38:38PM -0800, Montassar Dridi wrote:
> I tried different port, still getting the issue
If you get "Address* already in use", then really it is already in use. Either
by the other pod or something else on your deployment. But there is really no
other option.
--
You rec
I tried different port, still getting the issue
also when I restart the server inside the second application pod, I can see
the website live for the second application but not for the first one.
do you know of any tutorial or a sample yaml files for a similar case that
I can follow and try to wor
I tried different port, still getting the issue
also when I restart the server inside the second application pod, I can see
the website live for the second application but not for the first one.
do you know of any tutorial or a sample yaml files for a similar case that
I can follow and try to wor
The two containers share a network namespace, so each application needs to
listen on a different port, they can't both bind to port 80.
On Thu, Mar 2, 2017 at 6:36 PM, Montassar Dridi
wrote:
> I'm trying to create two containers (tomact image) inside my web pod:
> each one going to run a java ap
I'm trying to create two containers (tomact image) inside my web pod:
each one going to run a java application but I want them to share the same
ip address
apiVersion: extensions/v1beta1
kind: Deployment
metadata:
name: web-dp
labels:
name: web-pod
version: v1
spec:
template:
m
