# Using external\_links in sidekick containers

**URL:** <https://forums.suse.com/t/using-external-links-in-sidekick-containers/2548>\
**Category:** Rancher 1.x\
**Created:** [April 21, 2016, 8:03am UTC](https://forums.suse.com/t/using-external-links-in-sidekick-containers/2548 "2016-04-21T08:03:23Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![moensch](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/moensch/32/1787_2.png) [@moensch](https://forums.suse.com/u/moensch)\
**Post date:** [April 21, 2016, 8:03am UTC](https://forums.suse.com/t/using-external-links-in-sidekick-containers/2548/1 "2016-04-21T08:03:23Z")

</div>

I was able to successfully use external\_links in services to add an alias to a service in a different stack:

```
external_links:
 - otherstack/someservice:alias

```

However, once I mark this container as a sidekick, external\_links no longer seem to work (I can still ping “someservice.otherstack”, but I cannot ping “alias” anymore).

Is this a known limitation or potentially a bug?

---

<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:** [April 21, 2016, 7:15pm UTC](https://forums.suse.com/t/using-external-links-in-sidekick-containers/2548/2 "2016-04-21T19:15:07Z")

</div>

You are unable to set links on the sidekick (as the UI shows), but you can add the links in the primary service. Even though the link is set at the primary service level, the sidekick will be able to ping the alias.
