# Install convoy volume driver

**URL:** <https://forums.suse.com/t/install-convoy-volume-driver/460>\
**Category:** RancherOS\
**Created:** [September 13, 2015, 11:32am UTC](https://forums.suse.com/t/install-convoy-volume-driver/460 "2015-09-13T11:32:25Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![pwFoo](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/pwfoo/32/2884_2.png) [@pwFoo](https://forums.suse.com/u/pwFoo)\
**Post date:** [September 13, 2015, 11:32am UTC](https://forums.suse.com/t/install-convoy-volume-driver/460/1 "2015-09-13T11:32:25Z")

</div>

I tested convoy volume driver with RancherOS and it works fine! Changes are persistent, services can share persistent convoy volumes (for example apache container as /var/www/html and ssh container to change web content).

But my convoy plugin wasn’t installed reboot save.  
How can I

- persistent save /usr/bin/convoy and /usr/bin/convoy-pdata\_tools?
- start convoy daemon an RancherOS startup?

Could it added as RancherOS os-service? Or how to install it native in RancherOS?

---

<div class="post-metadata">

**Author:** ![ndelitski](https://avatars.discourse-cdn.com/v4/letter/n/f04885/32.png) [@ndelitski](https://forums.suse.com/u/ndelitski)\
**Post date:** [October 10, 2015, 4:31pm UTC](https://forums.suse.com/t/install-convoy-volume-driver/460/2 "2015-10-10T16:31:09Z")

</div>

+1 Did you find any solution yet?

---

<div class="post-metadata">

**Author:** ![pwFoo](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/pwfoo/32/2884_2.png) [@pwFoo](https://forums.suse.com/u/pwFoo)\
**Post date:** [October 10, 2015, 4:46pm UTC](https://forums.suse.com/t/install-convoy-volume-driver/460/3 "2015-10-10T16:46:45Z")

</div>

I build an quick and dirty, but working docker image to use with RancherOS system-docker.  
[http://forums.suse.com/t/add-binary-to-rancheros-as-os-service/501/3](http://forums.suse.com/t/add-binary-to-rancheros-as-os-service/501/3)

I have some improvements in mind, but need a way to start the convoy container before (user-)docker. I know how to start it after another container (just with a container link), but not how to start it before…
