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.

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

Cannot submit a container to be started #30

Closed
tlaufkoetter opened this issue May 3, 2016 · 2 comments
Closed

Cannot submit a container to be started #30

tlaufkoetter opened this issue May 3, 2016 · 2 comments
Assignees

Comments

@tlaufkoetter
Copy link
Contributor

Chronos response has the status 500.

@pbelmann pbelmann self-assigned this Jun 7, 2016
@pbelmann
Copy link
Member

pbelmann commented Jun 7, 2016

I could not reproduce this error.
If this is the fault of your chronos configuration I created issue #38 in order to show the configuration that definitely works with jobproxy.

Please reopen if you still encounter this issue.

@pbelmann
Copy link
Member

pbelmann commented Jun 7, 2016

By the way the following xml works for me:

<task>
    <user>test</user>
    <cores>1</cores>
    <memory>128</memory>
    <cputime>10</cputime>
    <cmd>sleep 40</cmd>
    <container>
            <image>ubuntu</image>
    </container>
</task>

@pbelmann pbelmann closed this as completed Jun 7, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants