-
Notifications
You must be signed in to change notification settings - Fork 384
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
Add RestartPolicy parameter to Create Container #8
Comments
Well that's annoying. I would have remembered seeing that. Want me to roll On Monday, October 6, 2014, Ahmet Alp Balkan [email protected]
|
That needs to be tested as well. If you'd like to work on it, you can send a separate CR off from clean |
Understood. On Monday, October 6, 2014, Ahmet Alp Balkan [email protected]
|
I'll be submitting a PR for this shortly. |
@jgarverick based on the revelations from the issue on docker/docker, will you be updating the code? thanks. |
Since this particular change isn't due to go in until v1.3 (API v1.15), I On Thu, Oct 16, 2014 at 2:47 AM, Ahmet Alp Balkan [email protected]
|
You're so lucky 1.3 is released today! :-) |
Who would have thought? I'm on it. On Thursday, October 16, 2014, Ahmet Alp Balkan [email protected]
|
This has been checked in and tested. Should be good to go. LMK if you On Thu, Oct 16, 2014 at 7:28 PM, Josh Garverick [email protected]
|
Great, I have a few changes that I need to make about creation of restartpolicy object. I believe I will just merge yours and apply on top of it. Thanks On Tue, Oct 21, 2014 at 10:43 AM, Josh Garverick [email protected]
|
Sounds good. Cheers! On Tuesday, October 21, 2014, Ahmet Alp Balkan [email protected]
|
Fixed now in |
Setup to generate documentation
This has just randomly showed up in API 1.14 docs. I am not even sure why they modify docs after releasing it. It surely wasn't there before... https://docs.docker.com/reference/api/docker_remote_api_v1.14/#create-a-container
The text was updated successfully, but these errors were encountered: