...and here's the pod's description:
Name: dictionary-10-b3go6
Namespace: ieml-dev
Image(s):
172.30.171.126:5000/ieml-dev/dictionary@sha256:b1566af562a870eb94d4c2f46f47a46fb391876ce809d2c715762c5b88aa9083
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:
Container ID:
docker://2d310c466110f63d7ff9b563fb234b5f70e98ec87f60a0484324d3271c02766d
Image:
172.30.171.126:5000/ieml-dev/dictionary@sha256:b1566af562a870eb94d4c2f46f47a46fb391876ce809d2c715762c5b88aa9083
Image ID:
docker://381b13bef679d6075d64c14508a01015281d6e7c6104cec164f596bb142c3bde
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 <[email protected]> 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 <[email protected]
> <mailto:[email protected]>> wrote:
> I was expecting I could access the service through
>
> http://dictionary-ieml-dev.apps.intrinsic.world/
> <http://dictionary-ieml-dev.apps.intrinsic.world/>
>
>
>> On 07 Jun 2016, at 16:11, Clayton Coleman <[email protected]
>> <mailto:[email protected]>> wrote:
>>
>> From the outside, what are you trying to curl?
>>
>> On Tue, Jun 7, 2016 at 9:32 AM, Candide Kemmler <[email protected]
>> <mailto:[email protected]>> 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:
>>
>> https://gist.github.com/anonymous/d76d9c04c7417bc8bcf455b91db70424
>> <https://gist.github.com/anonymous/d76d9c04c7417bc8bcf455b91db70424>
>>
>> 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
>> [email protected] <mailto:[email protected]>
>> http://lists.openshift.redhat.com/openshiftmm/listinfo/users
>> <http://lists.openshift.redhat.com/openshiftmm/listinfo/users>
>>
>>
>
>
_______________________________________________
users mailing list
[email protected]
http://lists.openshift.redhat.com/openshiftmm/listinfo/users
