# Support for running commands in different namespaces remotely

**URL:** <https://forum.ansible.com/t/support-for-running-commands-in-different-namespaces-remotely/17847>\
**Category:** Ansible Project\
**Created:** [March 26, 2015, 1:24pm UTC](https://forum.ansible.com/t/support-for-running-commands-in-different-namespaces-remotely/17847 "2015-03-26T13:24:51Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Bjornar\_Ness](https://avatars.discourse-cdn.com/v4/letter/b/f04885/32.png) [@Bjornar\_Ness](https://forum.ansible.com/u/Bjornar_Ness)\
**Post date:** [March 26, 2015, 1:24pm UTC](https://forum.ansible.com/t/support-for-running-commands-in-different-namespaces-remotely/17847/1 "2015-03-26T13:24:51Z")

</div>

Is any work beeing done on enabling running a task in a remote namespace (setns)?

Reason I am asking is I have a network oob namespace sshd is running in, and for  
some of the ansible tasks I would like beeing able to specify for example:

- namespace: netns=default

…which should cause all commands of this task to be run in a shell created by:

ip netns exec default sh

eventually

ip netns exec default {{ original\_command }}