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
Systemd socket activation and .service/.socket files #2054
Conversation
@@ -28,7 +28,7 @@ func open() (pty, tty *os.File, err error) { | |||
return nil, nil, err | |||
} | |||
|
|||
t, err := os.OpenFile(sname, os.O_RDWR, 0) | |||
t, err := os.OpenFile(sname, os.O_RDWR|syscall.O_NOCTTY, 0) |
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 really needed for this PR ?
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.
I would have to agree with @vieux here - I think we should only touch vendor/
to update from upstream code. If upstream can't move quickly enough, then we have to evaluate making our own fork and changing our upstream. If this is a problem for this PR, then it needs to be blocked on #1422, and we need to resolve that upstream (ie kr/pty#9).
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.
See #2066.
Whoops amending that commit seemed to have deleted your comments. I tried to sneak that in on the basis that the upstream one would have been fixed anyway. It's not really required but otherwise just has the same issue as #1422 . |
The comments are still there on "an outdated diff". Github figures that you amended that line to fix our concerns (which you did), so the outdated comments are hidden. 👍 |
Hey @canoon, sorry for the slow review. I really want to get this merged. Here are some comments:
How about this prototype:
If you can put that in Thanks! |
@canoon @tianon If neither of you are taking this I can do it. Also, we have a go-systemd library with an activation package: https://github.com/coreos/go-systemd/ |
Here is a quick implementation of the ListenFD function: https://github.com/philips/docker/compare/add-socket-activation @shykes Where is the refactoring taking place so I can try and fit this in? |
Bump. |
Back from the 0.7 craziness. @philips it looks like nobody is active on this so feel free to dive in :) |
@canoon can you rebase and use the |
@vieux Docker is implementing a systemd library? We already have a systemd library that has socket activation with tests and I was going to use that. https://github.com/coreos/go-systemd |
@philips it's just a subdir for the systemd-specific parts of docker. On Thu, Dec 5, 2013 at 11:31 AM, Victor Vieux notifications@github.com
|
@philips Does your new PR completely replace this one ? |
@crosbymichael Yes. |
Closing in favor of #3105 |
Like #1534 but adds in socket activation via systemd. Allows systemd to just open the socket and launch docker when required.