# Convoy-gluster activating **URL:** \ **Category:** Convoy\ **Created:** [April 15, 2016, 9:31pm UTC](https://forums.suse.com/t/convoy-gluster-activating/2484 "2016-04-15T21:31:25Z")\ **Posts on this page:** 11\ **Page:** 1
**Author:** ![brdlfg](https://avatars.discourse-cdn.com/v4/letter/b/e99b99/32.png) [@brdlfg](https://forums.suse.com/u/brdlfg)\ **Post date:** [April 15, 2016, 9:31pm UTC](https://forums.suse.com/t/convoy-gluster-activating/2484/1 "2016-04-15T21:31:25Z")
First time deploy here of convoy-gluster. The glusterfs containers are up and fine. The logs on the convoy-gluster containers just keep repeating this. Rebuilt the system with another set of VMs to test again and have the same issue. the convoy-gluster-storagepool container starts fine. 4/15/2016 2:30:20 PMWaiting for metadata 4/15/2016 2:30:20 PMtime=“2016-04-15T20:30:20Z” level=fatal msg="open /host/var/run/docker/execdriver/native: no such file or directory" 4/15/2016 2:31:48 PMWaiting for metadata 4/15/2016 2:31:49 PMtime=“2016-04-15T20:31:49Z” level=fatal msg="open /host/var/run/docker/execdriver/native: no such file or directory" 4/15/2016 2:33:49 PMWaiting for metadata 4/15/2016 2:33:51 PMtime=“2016-04-15T20:33:51Z” level=fatal msg="open /host/var/run/docker/execdriver/native: no such file or directory" 4/15/2016 3:12:39 PMWaiting for metadata 4/15/2016 3:12:41 PMtime=“2016-04-15T21:12:41Z” level=fatal msg="open /host/var/run/docker/execdriver/native: no such file or directory" 4/15/2016 3:13:06 PMWaiting for metadata 4/15/2016 3:13:06 PMtime=“2016-04-15T21:13:06Z” level=fatal msg=“open /host/var/run/docker/execdriver/native: no such file or directory” ---
**Author:** ![cjellick](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/cjellick/32/2876_2.png) [@cjellick](https://forums.suse.com/u/cjellick)\ **Post date:** [April 15, 2016, 9:51pm UTC](https://forums.suse.com/t/convoy-gluster-activating/2484/2 "2016-04-15T21:51:31Z")
Yup. It looks like we have an issue with convoy and docker 1.11. Are you using docker 1.11? > We are currently officially supporting Docker 1.10.3. ---
**Author:** ![brdlfg](https://avatars.discourse-cdn.com/v4/letter/b/e99b99/32.png) [@brdlfg](https://forums.suse.com/u/brdlfg)\ **Post date:** [April 15, 2016, 10:37pm UTC](https://forums.suse.com/t/convoy-gluster-activating/2484/3 "2016-04-15T22:37:16Z")
Thank you, that is the issue. ---
**Author:** ![Fred](https://avatars.discourse-cdn.com/v4/letter/f/db5fbb/32.png) [@Fred](https://forums.suse.com/u/Fred)\ **Post date:** [April 20, 2016, 5:42pm UTC](https://forums.suse.com/t/convoy-gluster-activating/2484/4 "2016-04-20T17:42:58Z")
Same error. Using Docker 1.11 ---
**Author:** ![weitzj](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/weitzj/32/1214_2.png) [@weitzj](https://forums.suse.com/u/weitzj)\ **Post date:** [May 1, 2016, 10:10am UTC](https://forums.suse.com/t/convoy-gluster-activating/2484/5 "2016-05-01T10:10:24Z")
Same here. Using Docker 1.11 ---
**Author:** ![kjellrichard](https://avatars.discourse-cdn.com/v4/letter/k/958977/32.png) [@kjellrichard](https://forums.suse.com/u/kjellrichard)\ **Post date:** [June 13, 2016, 11:44am UTC](https://forums.suse.com/t/convoy-gluster-activating/2484/6 "2016-06-13T11:44:21Z")
We have the same issue. Any ETA for Docker 1.11 support ---
**Author:** ![denise](https://avatars.discourse-cdn.com/v4/letter/d/82dd89/32.png) [@denise](https://forums.suse.com/u/denise)\ **Post date:** [June 14, 2016, 4:21am UTC](https://forums.suse.com/t/convoy-gluster-activating/2484/7 "2016-06-14T04:21:40Z")
Docker 1.11 support is to come in the next release of Rancher. [https://github.com/rancher/rancher/issues/4491](https://github.com/rancher/rancher/issues/4491) ---
**Author:** ![WolfgangL](https://avatars.discourse-cdn.com/v4/letter/w/96bed5/32.png) [@WolfgangL](https://forums.suse.com/u/WolfgangL)\ **Post date:** [July 5, 2016, 12:53pm UTC](https://forums.suse.com/t/convoy-gluster-activating/2484/8 "2016-07-05T12:53:59Z")
I had a try on rancherOS 0.5.0 that inludes Docker 1.11 but It look as if the issue is still there. ---
**Author:** ![grayloon](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/grayloon/32/1449_2.png) [@grayloon](https://forums.suse.com/u/grayloon)\ **Post date:** [July 7, 2016, 11:49am UTC](https://forums.suse.com/t/convoy-gluster-activating/2484/9 "2016-07-07T11:49:41Z")
Not sure if this is related, but… I had issues last week with Convoy/GlusterFS on a vSphere setup with Docker 1.11. I killed the whole setup and recreated it with Rancher 1.1.0 and boot2docker 1.11.2 yesterday. I created a GlusterFS stack with no issues. When I try to set up Convoy GlusterFS stack, it never completes. convoy-gluster-storagepool is stuck on initializing, and convoy-gluster is stuck on activating. Any suggestions to get this working? ---
**Author:** ![grayloon](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/grayloon/32/1449_2.png) [@grayloon](https://forums.suse.com/u/grayloon)\ **Post date:** [July 7, 2016, 1:45pm UTC](https://forums.suse.com/t/convoy-gluster-activating/2484/10 "2016-07-07T13:45:52Z")
Here’s some log output if it helps… **From convoy-gluster\_convoy-gluster-storagepool\_1:** `7/7/2016 8:43:22 AMWaiting for metadata 7/7/2016 8:43:22 AMtime="2016-07-07T13:43:22Z" level=info msg="Listening for health checks on 0.0.0.0:10241/healthcheck" 7/7/2016 8:43:22 AMtime="2016-07-07T13:43:22Z" level=info msg="Socket file: /host/var/run/convoy-convoy-gluster.sock" 7/7/2016 8:43:23 AMtime="2016-07-07T13:43:23Z" level=info msg="Initializing event router" workerCount=10 7/7/2016 8:43:23 AMtime="2016-07-07T13:43:23Z" level=info msg="Connection established" 7/7/2016 8:43:28 AMtime="2016-07-07T13:43:28Z" level=debug msg="storagepool event [dcf3e939-2021-46bc-8dde-87880599770f 34e3f4aa-234f-4a6f-a436-e4498f1f4111 8e9dc6af-0232-4ea6-978f-0d56281abd8d]"` **From convoy-gluster\_convoy-gluster\_1:** `7/7/2016 8:43:32 AMWaiting for metadata 7/7/2016 8:43:32 AMtime="2016-07-07T13:43:32Z" level=fatal msg="open /host/var/run/docker/execdriver/native: no such file or directory"` ---
**Author:** ![grayloon](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/grayloon/32/1449_2.png) [@grayloon](https://forums.suse.com/u/grayloon)\ **Post date:** [July 12, 2016, 6:54pm UTC](https://forums.suse.com/t/convoy-gluster-activating/2484/11 "2016-07-12T18:54:36Z")
This boot2docker tweak solved my issue, but it was a pain to track down. > [@How to get Rancher overlay network working locally](http://forums.suse.com/t/how-to-get-rancher-overlay-network-working-locally/3044/12): > > Reading this [1] made me understand how to build a boot2docker image. I took the following steps: cloned the boot2docker repo switched to the v1.10.3 tag edited the kernel\_config to set CONFIG\_INET\_XFRM\_MODE\_TRANSPORT=yes built a new boot2docker.iso started two VMs using this (host3/host4) extended my Solr service to run on hosts 3/4 When I attempted to ping the host4 network agent from the host3 network agent, I still got no response. Likewise, the Solr instances cannot see each other on th…