Yes, and I can ssh to it and from there I can do `curl localhost:8080` no problems.
Here's my Dockerfile btw: https://gist.github.com/anonymous/6332b3cd89d0a7847890e71e3b7d4a0c <https://gist.github.com/anonymous/6332b3cd89d0a7847890e71e3b7d4a0c> > 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
