search

rancher / convoy

A Docker volume plugin, managing persistent container volumes.
Apache License 2.0
1.31k stars 135 forks source link

ERRO[0100] http server erroraccept unix /var/run/convoy/convoy.sock: use of closed network connection pkg=daemon #222

Closed michaellacastro closed 6 years ago

michaellacastro commented 6 years ago

Information: VM OS: Centos 7 docker --version: Docker version 17.09.0-ce, build afdb6d4

Problem

Hello, I have recently tried to install Convoy and followed the quick start guide and when I execute the sudo command to start the daemon for the COnvoy plugin sudo convoy daemon --drivers devicemapper --driver-opts dm.datadev=/dev/loop5 --driver-opts dm.metadatadev=/dev/loop6

it returns this output screen shot 2017-11-20 at 9 28 04 am

and when I cancel it outputs: screen shot 2017-11-20 at 9 28 32 am

Points:

  1. I tried even shutting of my firewall with the VM, nope.

  2. Checked the .sock file screen shot 2017-11-20 at 9 28 51 am

  3. Checked the directory screen shot 2017-11-20 at 9 29 26 am

--

Question: What could I be missing? Am I doing something wrong? I have tried it on 2 other VMs and its still not working and I dont know what it means please help :<. Thank you!

Blessings

yasker commented 6 years ago

Convoy daemon is running as a daemon, so it will continue running until you stop it.

You can run Convoy daemon in one console or start it as a service, then use Convoy (cli) to connect to it. Or create Docker volume with it.

michaellacastro commented 6 years ago

Wait isnt running this command : "sudo convoy daemon --drivers devicemapper --driver-opts dm.datadev=/dev/loop5 --driver-opts dm.metadatadev=/dev/loop6" supposed to start it? My problem is that I cant start it. I get stuck in this step and I dont know whats wrong

michaellacastro commented 6 years ago

screen shot 2017-11-21 at 9 08 47 am

cause if i run it in a window and try a convoy command in another window it appears like this

Gapmeister66 commented 4 years ago

I'm late to the party but I think that yasker means you should run the daemon in the background somehow:

e.g convoy daemon --drivers devicemapper --driver-opts dm.datadev=/dev/loop5 --driver-opts dm.metadatadev=/dev/loop6 &

When it hangs it is actually still running correctly, so killing it is not what you want to do :) Once I realised this I was able to continue to:

docker run -v vol1:/vol1 --volume-driver=convoy alpine touch /vol1/foo

Instructions at: https://github.com/rancher/convoy