Public Repository

Last pushed: 2 months ago
Short Description
Chronos on top of mesosphere/mesos
Full Description

Usage

$ dcos package install chronos

or

$ docker run --net=host -e PORT0=8080 -e PORT1=8081 mesosphere/chronos:v3.0.0 --zk_hosts $zk_ip:2181 --master zk://$zk_ip:2181/mesos
Docker Pull Command
Owner
mesosphere

Comments (11)
aayore
4 months ago

I got mine to work by omitting the --net=host:

docker run -e PORT0=4400 -e PORT1=8081 --name chronos.service -p 4400:4400 -p 8081:8081 mesosphere/chronos:v3.0.0 --zk_hosts=master1:2181,master2:2181,master3:2181 --master=zk://master1:2181,master2:2181,master3:2181/mesos --hostname=master1 --mesos_role=private --mesos_framework_name=chronos
docker run -e PORT0=4400 -e PORT1=8081 --name chronos.service -p 4400:4400 -p 8081:8081 mesosphere/chronos:v3.0.0 --zk_hosts=master1:2181,master2:2181,master3:2181 --master=zk://master1:2181,master2:2181,master3:2181/mesos --hostname=master2 --mesos_role=private --mesos_framework_name=chronos
docker run -e PORT0=4400 -e PORT1=8081 --name chronos.service -p 4400:4400 -p 8081:8081 mesosphere/chronos:v3.0.0 --zk_hosts=master1:2181,master2:2181,master3:2181 --master=zk://master1:2181,master2:2181,master3:2181/mesos --hostname=master3 --mesos_role=private --mesos_framework_name=chronos

I had to include the --mesos_role because I'm running my Mesos cluster under a custom role.

agarbato
4 months ago

Same error here :

[scallop] Error: Bad arguments for option 'http_port': '' - you should provide exactly one argument

This image 3.0 is broken and lack of documentation make it impossible to use. Please provide documentation or at least docker run with working parameters and a Dockerfile.

mvanholsteijn
5 months ago

Trying to run a v3.0.0 chronos image resultsi n the following error:

[scallop] Error: Bad arguments for option 'http_port': '' - you should provide exactly one argument

It work perfectly with the previous version of this image.

wangqiang8511
2 years ago

Sorry, false alarm. It works perfect with --hostname $(hostname -i) When you have flannel or openvswitch enabled with your mesos setup.

wangqiang8511
2 years ago

This container works perfect if I only start one instance in marathon. I have issues when I start multiple chronos instances in marathon to achieve HA, since the hostname registered in zookeeper is docker id. This hostname is not reachable from other hosts. Then the redirect function doesn't work. Correct me if I did the configuration wrongly.

cfortier
2 years ago

@nickpoorman : That syntax is wrong. You need zk://<comma separated list of ip:port>/mesos

Example: zk://10.0.1.101:2181,10.0.1.102:2181,10.0.1.103:2181/mesos

nickpoorman
2 years ago

Just a heads up, for some reason the debian package has master already set as a localhost variable so when you go to run /usr/bin/chronos you get his error when trying to set --master:

Error: Bad arguments for option 'master': 'zk://localhost:2181/mesos zk://zoo1:2181,zoo2:2181,zoo3:2181/mesos' - you should provide exactly one argument for this option
cody4mesos
2 years ago

As far as an automated build goes, the problem is to run the framework in production you need to make sure the framework is built against the same (or one prior) version of libmesos that the masters in the cluster are running. So we need the build to be triggered both by changes in chronos version as well as changes in mesos version. (So for chronos 2.3.2 we should have a build against mesos 0.21 and 0.22 so you can use it on your old cluster, then when you do a mesos upgrade, then do a chronos framework update to rollout the new libmesos)

nicgrayson
2 years ago

Is there a reason this isn't an automated build using the dockerfile in the repo?