Closed 23tux closed 8 years ago
I found this issue https://github.com/burke/zeus/issues/488 which solved my problem.
The key was to set the ZEUSSOCK
to a path which is NOT mounted through Virtual Box. My docker-compose.override.yml
looks now like this:
my_app:
environment:
ZEUSSOCK: /zeus/.zeus.sock
note: You have to create /zeus
by hand.
Hi,
when I try to run
zeus start
inside my docker container, it crashes withI checked, and there is NO
zeus.sock
file present. The strange thing is, that a.zeus.soc
is created (note the missingk
):I'm running docker on top of a
ruby:2.1
image on OS X using docker-machine version 0.6.0, build e27fb87 and Docker version 1.10.0, build 590d5108.I'm bashing inside my container with
docker exec -it my_container bash
and runzeus start
, then the error above occurs.Running zeus inside the same container on a Linux machine works perfect.
Anybody an idea?