Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

launching a container through the marathon api fails #47

Closed
mjvdende opened this issue Jan 29, 2015 · 3 comments
Closed

launching a container through the marathon api fails #47

mjvdende opened this issue Jan 29, 2015 · 3 comments

Comments

@mjvdende
Copy link

Increase the marathon command line option --task_launch_timeout to at least the executor timeout you set on your slaves in the previous step.
@mjvdende
Copy link
Author

marathon v0.8.0.rc2 fixes this (https://github.com/mesosphere/marathon/releases/tag/v0.8.0-RC2)

@everpeace
Copy link
Owner

You can just add --task_launch_timeout 300000 to this line in Vagrantfile.

@everpeace
Copy link
Owner

I updated Marathon version to 0.8.0. I think this has been resolved by this.
If you see some issues on this, please feel free to re-open this.

mjvdende added a commit to mjvdende/vagrant-mesos that referenced this issue Feb 20, 2015
@mjvdende
fix everpeace#47
707d563
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@everpeace @mjvdende