# How can you use the drone extensions on non-docker (ssh) runners?

**URL:** <https://drone.discourse.group/t/how-can-you-use-the-drone-extensions-on-non-docker-ssh-runners/8348>\
**Category:** Drone Support\
**Created:** [April 24, 2021, 1:08pm UTC](https://drone.discourse.group/t/how-can-you-use-the-drone-extensions-on-non-docker-ssh-runners/8348 "2021-04-24T13:08:32Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![ohsayan](https://yyz1.discourse-cdn.com/flex003/user_avatar/drone.discourse.group/ohsayan/32/2887_2.png) [@ohsayan](https://drone.discourse.group/u/ohsayan)\
**Post date:** [April 24, 2021, 1:08pm UTC](https://drone.discourse.group/t/how-can-you-use-the-drone-extensions-on-non-docker-ssh-runners/8348/1 "2021-04-24T13:08:32Z")

</div>

I find Drone’s plugin ecosystem to be quite amazing. However, the only drawback (AFAIK) is that we can’t use the plugins on non-docker (SSH runners for example) runners (or am I falling out and missing out on something?).  
This is quite a problem as we intend to use things like GitHub Release, GitHub Issue, etc and the only way for us to do this now is via manually running `curl` commands which is quite cumbersome. Provided that there is such a great plugin ecosystem, why can’t we get this running on non-docker pipelines?

Any help and/or guidance is greatly appreciated