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

Cancelling a job does not invoke the clean up phase #676

Open
davemackintosh opened this issue Dec 19, 2014 · 13 comments
Open

Cancelling a job does not invoke the clean up phase #676

davemackintosh opened this issue Dec 19, 2014 · 13 comments
Labels

Comments

@davemackintosh
Copy link

When cancelling a job it does not run the clean up method, when using Docker this leaves problematic images/containers clogging the system up.

Also, if an unexpected error occurs it does not invoke the clean up phase, this might be verbiage in the custom scripts plugin stating "Cleanup always runs."

@davemackintosh
Copy link
Author

Anyone looking into this? Maybe I could be assigned?

@kfatehi
Copy link
Member

kfatehi commented Jan 13, 2015

@davemackintosh I don't think anyone is looking into it. You're right, the problem still exists from back when we built the main guts of the docker runner (about 5 months ago).

I just granted you write access to the main repo as well as strider-docker-runner and assigned you to this issue. good luck let me know if i can be of any further assistance: I'm also always in the IRC channel as keyvan and get push notifications on my phone if you write my name.

@davemackintosh
Copy link
Author

Thanks dude, I'll be around if you have any questions as well.

@davemackintosh
Copy link
Author

I'm stopping work on this as I can't resolve an issue with the docker-modem integration while using boot2docker on OSx.

@knownasilya
Copy link
Member

@davemackintosh what's the issue?

@davemackintosh
Copy link
Author

docker-modem doesn't seem to support the tcp protocol, I can access my docker rest api but for some reason docker-modem cannot and I spent wayy too long trying to figure out what was going on before stopping

@knownasilya
Copy link
Member

It does, apocas/docker-modem#31 (comment)

@davemackintosh
Copy link
Author

Interesting, I guess the dependency in dockerode is out of date then as I did a manual install of the latest dockerode and still had the same problem. I'll try a manual install of the latest docker-modem in a bit and continue work if it fixes the problem and I'll submit a PR to dockerode I can see it says 0.1.x but maybe it should be ~0.1.22 so it can still get patches.

@knownasilya
Copy link
Member

I think you mean ^0.1.22 which will work up to but not including 1.0.

@davemackintosh
Copy link
Author

Doesn't that mean you'll get minor revisions as well which might have breaking changes?

@knownasilya
Copy link
Member

Technically minor shouldn't have breaking changes, since those are new features. Breaking changes should increment major. But every project is different and it depends how dockerode is managed.

@davemackintosh
Copy link
Author

I'll look in a bit, some client work to do before hand which is more important.

@corradio
Copy link

corradio commented Jun 4, 2018

Hi all, this is very needed. Anyone has had some success?

@davemackintosh davemackintosh removed their assignment Oct 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants