-
Notifications
You must be signed in to change notification settings - Fork 61
Chronos keeps failing #520
Comments
@maasg Chronos fails with the following error
Any idea? |
The option |
See https://github.com/ContainerSolutions/minimesos/blob/master/opt/apps/chronos.json. It seems Mesos adds an extra |
I think the port 4400 port should be removed from the Marathon file. We don't know in advance which port it will get assigned. |
Something changed in the chronos port exposure ( echo "---> start chronos"
docker run -d \
-e PORT0=4400 \
-e PORT1=8081 \
--name chronos --restart always \
-p 4400:4400 \
-p 8081:8081 \
mesosphere/chronos:v3.0.1 \
--zk_hosts=${MESOS_MASTER_1}:2181 \
--master=zk://${MESOS_MASTER_1}:2181/mesos \
--hostname=${MESOS_MASTER_1} \
--mesos_role=private \
--mesos_framework_name=chronos Snippet from https://mesos.github.io/chronos/docs/
Your previous link to the chronos blob no longer works, so I can't verify. Hope this helps @frankscholten and you can add chronos to minimesos |
Thanks for the heads up @blijblijblij, I will have a look soon. |
No description provided.
The text was updated successfully, but these errors were encountered: