-
Notifications
You must be signed in to change notification settings - Fork 5.3k
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 restart option to Fig. #594
Conversation
Hello! Thanks for this. It looks like the option to |
9d0ea1c
to
7b91175
Compare
Hi @bfirsh! Indeed it's Cheers! |
👍 @bfirsh any chance this could make it in the 1.0.1 release? Will that be at the same time as the Docker 1.3.1? |
I think we'll release 1.0.1 as a quick bugfix release as soon as dockerpty is ready. We can then put this into a larger 1.1 feature release. |
Guess I'll have to be patient then, or look into compiling fig myself :) |
I have to admit that I would have loved to see this in 1.0.1 too. If we consider that Fig should be in sync with the docker releases, then this is a bug fix and not a new feature 😄 |
Fig isn't in sync with Docker. |
It might make it into 1.0.1, but it's not going to be a blocker for a bugfix release, that's all. I would quite like to make 1.0.x bug fix releases and 1.x.0 feature releases, as per semantic versioning (and how Docker does it). |
Yes I thought so and agree clearly with your point. Obviously this is a new feature for Fig. Thus should be in a 1.x.0 release. Thanks for your work !
|
Though that's not to disregard your PR. I really want this too. ;) Currently figuring out how to get our CI system to run the damn test suite. The tests run fine locally, so I think this is okay. |
if len(parts) == 2: | ||
name, max_retry_count = parts | ||
else: | ||
name, = parts |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Stray comma here
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Because I don't want the List
but the only element inside
>>> a, = ['hello']
>>> a
'hello'
>>> a = ['hello']
>>> a
['hello']
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh, neat.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
name = parts[0] is much clearer. ;) Not a big deal.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fair enough :)
7b91175
to
cc003a4
Compare
I pushed force the first commit and pushed normally the second one, hope this forces the tests to run |
That worked. https://app.wercker.com/#build/5451078547c2f0c812105681 Looks like commit statuses are broken. Thanks! |
Oh yeah. Weird. |
@bfirsh any chance to get this merged in? |
LGTM |
I'm not seeing a way to force the build, but @popox if you |
f457057
to
8bda279
Compare
35793f1
to
b9bd478
Compare
@dnephin commit amending didn't do the trick, so I just squashed and rebased on master. |
Signed-off-by: Paul Bonaud <paul@bonaud.fr>
b9bd478
to
04da6b0
Compare
The build is launched on my fork but not on the PR. |
Cool, works for me, looks good |
@@ -142,7 +142,7 @@ dns: | |||
- 9.9.9.9 | |||
``` | |||
|
|||
### working\_dir, entrypoint, user, hostname, domainname, mem\_limit, privileged | |||
### working\_dir, entrypoint, user, hostname, domainname, mem\_limit, privileged, restart | |||
|
|||
Each of these is a single value, analogous to its [docker run](https://docs.docker.com/reference/run/) counterpart. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this still true? Thinking of :max_retry
here (or is that to be considered a "single" value? idk)
@dnephin is there anything needed to move this PR forward? I added two small suggestions, but apart from that, wondering if this is ready to merge? |
would be great to see this merged :) |
LGTM ping @bfirsh |
LGTM |
Thanks @popox! |
I wonder when this feature will be published? along with 1.1.0 milestone? I noticed that there is no due date for 1.1.0 milestone.. so is there a current walk-around besides using the HEAD version? |
+1 Neat feature and it would be good to see it in release version ASAP |
+1 |
Add restart option to Fig. Signed-off-by: Yuval Kohavi <yuval.kohavi@gmail.com>
Hello!
I simply find this project really good, and ended up needing the
restart
option (Related to #478).Since Docker 1.2 there is a
restart
option ondocker run
ning containers to add restart policies. I think fig options should be able to set restart policies to it's orchestrated containers.This PR adds the option in Fig.
Let me know if there it's all ok?