# \`nosuid\` fuse mount option deactivates \`capabilities\`

**URL:** <https://discourse.appimage.org/t/nosuid-fuse-mount-option-deactivates-capabilities/1652>\
**Category:** Creating AppImages\
**Created:** [April 19, 2020, 6:10pm UTC](https://discourse.appimage.org/t/nosuid-fuse-mount-option-deactivates-capabilities/1652 "2020-04-19T18:10:17Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![Hamid](https://avatars.discourse-cdn.com/v4/letter/h/5fc32e/32.png) [@Hamid](https://discourse.appimage.org/u/Hamid)\
**Post date:** [April 19, 2020, 6:10pm UTC](https://discourse.appimage.org/t/nosuid-fuse-mount-option-deactivates-capabilities/1652/1 "2020-04-19T18:10:17Z")

</div>

Hi all,

Assume that we want to make an AppImage from a binary which needs some Linux capabilities to run. For example `ping` needs `cap_net_raw` capability to be able to get run by a non-root user. Otherwise it will not run, saying: `ping: socket: Operation not permitted`!

Now if we make an AppImage of such a binary, even though you set capabilities for it beforehand, the AppImage would not run because it is mounted with `nosuid` fuse mount option and `nosuid` deactivates `capabilities`.

How can we make AppImages which mount without `nosuid`?

Any idea would be appreciated 😉

---

_[View the full topic](https://discourse.appimage.org/t/nosuid-fuse-mount-option-deactivates-capabilities/1652)._