[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: cannot expose docker service



I am also able to port forward locally... Really strange: the only thing that doesn't work is really the public route.

Any idea what I might have done wrong based on my template?

I doubt this is a bug, but not seeing any solution, I may file it as that anyway...


On 07 Jun 2016, at 17:48, Clayton Coleman <ccoleman redhat com> wrote:

So you see IP 10.1.2.20 listed in the endpoints for service your dictionary points to?  oc get endpoints SERVICE_NAME?

On Tue, Jun 7, 2016 at 10:38 AM, Candide Kemmler <candide intrinsic world> wrote:
...and here's the pod's description:

Name: dictionary-10-b3go6
Namespace: ieml-dev
Node: apps.intrinsic.world/167.114.241.106
Start Time: Tue, 07 Jun 2016 16:14:28 +0200
Labels: app=dictionary,deployment=dictionary-10,deploymentconfig=dictionary
Status: Running
Reason:
Message:
IP: 10.1.0.20
Replication Controllers: dictionary-10 (1/1 replicas created)
Containers:
  dictionary:
    QoS Tier:
      cpu: BestEffort
      memory: BestEffort
    State: Running
      Started: Tue, 07 Jun 2016 16:14:31 +0200
    Ready: True
    Restart Count: 0
    Environment Variables:
Conditions:
  Type Status
  Ready True 
Volumes:
  default-token-cqsfz:
    Type: Secret (a secret that should populate this volume)
    SecretName: default-token-cqsfz
Events:
  FirstSeen LastSeen Count From SubobjectPath Reason Message
  ───────── ──────── ───── ──── ───────────── ────── ───────
  22m 22m 1 {default-scheduler } Scheduled Successfully assigned dictionary-10-b3go6 to apps.intrinsic.world
  22m 22m 1 {kubelet apps.intrinsic.world} spec.containers{dictionary} Pulling pulling image "172.30.171.126:5000/ieml-dev/dictionary sha256:b1566af562a870eb94d4c2f46f47a46fb391876ce809d2c715762c5b88aa9083"
  22m 22m 1 {kubelet apps.intrinsic.world} spec.containers{dictionary} Pulled Successfully pulled image "172.30.171.126:5000/ieml-dev/dictionary sha256:b1566af562a870eb94d4c2f46f47a46fb391876ce809d2c715762c5b88aa9083"
  22m 22m 1 {kubelet apps.intrinsic.world} spec.containers{dictionary} Created Created container with docker id 2d310c466110
  22m 22m 1 {kubelet apps.intrinsic.world} spec.containers{dictionary} Started Started container with docker id 2d310c466110



On 07 Jun 2016, at 16:21, Clayton Coleman <ccoleman redhat com> wrote:

Ok, so you created a route, and the route pointed to your service?  If you look at the endpoints for your service, are there any listed (i.e., did any pods start correctly)?

On Tue, Jun 7, 2016 at 10:17 AM, Candide Kemmler <candide intrinsic world> wrote:
I was expecting I could access the service through



On 07 Jun 2016, at 16:11, Clayton Coleman <ccoleman redhat com> wrote:

From the outside, what are you trying to curl?

On Tue, Jun 7, 2016 at 9:32 AM, Candide Kemmler <candide intrinsic world> wrote:
I have trouble exposing a service as a docker container.

My Dockerfile ends with EXPOSE 8080 and I have a route using that port:


I don't see where I'm doing things differently and yet I can `curl localhost:8080` from the pod itself but not access it from the outside world where I'm consistently seeing a 503 Service Unavailable.

_______________________________________________
users mailing list
users lists openshift redhat com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users








[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]