# Accessing a Service on Containers

**URL:** <https://forums.suse.com/t/accessing-a-service-on-containers/8190>\
**Category:** Rancher 1.x\
**Created:** [January 10, 2018, 4:18pm UTC](https://forums.suse.com/t/accessing-a-service-on-containers/8190 "2018-01-10T16:18:27Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![ranchboy](https://avatars.discourse-cdn.com/v4/letter/r/82dd89/32.png) [@ranchboy](https://forums.suse.com/u/ranchboy)\
**Post date:** [January 10, 2018, 4:18pm UTC](https://forums.suse.com/t/accessing-a-service-on-containers/8190/1 "2018-01-10T16:18:27Z")

</div>

I created a tomcat container from a stack. I want to access the port on 3000 - the exposed port. I can see the container on the 10.xx.xx ip address but I want it available on my local network so my users can see it. What’s the best way in achieving that? On docker it was simply exposing it but the port doesn’t seem accessible on the hosts.

---

<div class="post-metadata">

**Author:** ![mkendzior\_isdc](https://avatars.discourse-cdn.com/v4/letter/m/5fc32e/32.png) [@mkendzior\_isdc](https://forums.suse.com/u/mkendzior_isdc)\
**Post date:** [January 29, 2018, 10:24pm UTC](https://forums.suse.com/t/accessing-a-service-on-containers/8190/2 "2018-01-29T22:24:01Z")

</div>

If you expose the port in the docker-compose.yml for you stack, it should be available on the host. If you have multiple containers running you could also use a rancher load balancer to expose the port and keep the ports private in the containers.