# Starting container/service with specific IP

**URL:** <https://forums.suse.com/t/starting-container-service-with-specific-ip/4123>\
**Category:** Rancher 1.x\
**Created:** [September 27, 2016, 11:35am UTC](https://forums.suse.com/t/starting-container-service-with-specific-ip/4123 "2016-09-27T11:35:21Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Mr.B](https://avatars.discourse-cdn.com/v4/letter/m/46a35a/32.png) [@Mr.B](https://forums.suse.com/u/Mr.B)\
**Post date:** [September 27, 2016, 11:35am UTC](https://forums.suse.com/t/starting-container-service-with-specific-ip/4123/1 "2016-09-27T11:35:22Z")

</div>

Hi,

I’m new with rancher so maybe the answer to my question has been already answered somewhere, but I didn’t found it, so here it is.

I want to start a container with specific service, but I need this service to be reachable all the time from outside world no matter on which rancher host the service is running on. I’m looking for a rancher based solution which under “no rancher/container” condition would be solved by cluster ware with two resources (service and IP address) floating between cluster nodes. With other words, I want reach rancher service from rancher not aware client all the time.

I hope, my problem description is clear enough. If not, let me know and I will try to explain it better.

Thanks for any suggestions

martin

---

<div class="post-metadata">

**Author:** ![danipolo](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/danipolo/32/1571_2.png) [@danipolo](https://forums.suse.com/u/danipolo)\
**Post date:** [September 29, 2016, 11:09am UTC](https://forums.suse.com/t/starting-container-service-with-specific-ip/4123/2 "2016-09-29T11:09:10Z")

</div>

+1 for this… I have the same situation.

---

<div class="post-metadata">

**Author:** ![denise](https://avatars.discourse-cdn.com/v4/letter/d/82dd89/32.png) [@denise](https://forums.suse.com/u/denise)\
**Post date:** [October 5, 2016, 3:41am UTC](https://forums.suse.com/t/starting-container-service-with-specific-ip/4123/3 "2016-10-05T03:41:12Z")

</div>

If there is an exposed port on your service, then you could look into running an external DNS solution.

Here’s an example using Route53 in AWS [http://docs.rancher.com/rancher/v1.2/en/cattle/external-dns-service/](http://docs.rancher.com/rancher/v1.2/en/cattle/external-dns-service/)

but in our community catalog, they have added many other providers that would do the same concept.