'service eventstore start' What I'm messing ?

Greetings,

I’m trying to setup an eventstore docker container running on Ubuntu 14.04 LTS.

I went through http://docs.geteventstore.com/server/3.3.0/installing-from-debian-repositories/
(I picked v3.3.0 snapshot) but when I enter

service eventstore start

``

I get

Rather than invoking init scripts through /etc/init.d, use the service(8)
utility, e.g. service eventstore start

Since the script you are attempting to invoke has been converted to an
Upstart job, you may also use the start(8) utility, e.g. start eventstore

``

No eventstore is running at the end.

Here’s my /etc/eventstore/eventstore.conf

MemDb: True
RunProjections: None
ClusterSize: 1

``

What I’m doing wrong here ?

Thanks for your time.

Yorick

Hi Yorick,

Do you have a file named eventstore in /etc/init? The scripts included in the package are upstart scripts, not SysV init scripts, so the reference to init.d does make sense - though since you’re using service eventstore start that’s unusual.

Does this work in a VM rather than in a Docker container?

James

Hi Yorick,

Do you have a file named eventstore in /etc/init? The scripts included in the package are upstart scripts, not SysV init scripts, so the reference to init.d does make sense - though since you’re using service eventstore start that’s unusual.

I got /etc/init/eventstore.conf.

Does this work in a VM rather than in a Docker container?

It works in a VM but doesn’t in Docker. I both tried 1.5 and 1.6.2 Docker versions

James

Regards,

Yorick

Hi Yorick,

Is there a reason why you’re running upstart inside your container instead of just running the eventstore process directly? If you’re containerising, I wouldn’t bother with a process manager.

Yup, mark the entrypoint as eventstored, or run that command on start. It seems like upstart and Docker don’t play especially nicely together.

Hi Yorick,

Is there a reason why you’re running upstart inside your container instead of just running the eventstore process directly? If you’re containerising, I wouldn’t bother with a process manager.

There isn’t a particular reason except making it works in my settings. At the end, I went with the ol’ fashion way.