-
Notifications
You must be signed in to change notification settings - Fork 2.9k
libpod: specify a detach keys sequence in libpod.conf #3324
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
libpod: specify a detach keys sequence in libpod.conf #3324
Conversation
|
Hi @marcov. Thanks for your PR. I'm waiting for a containers or openshift member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
Can one of the admins verify this patch?
|
docs/podman-attach.1.md
Outdated
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.
Change to specifying it in the **libpod.conf** file: see...
docs/podman-create.1.md
Outdated
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.
Same change as the run manpage
libpod/runtime.go
Outdated
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.
Completely unrelated to this PR, but what is this - doing in the TOML string... @baude you added this, right?
utils/utils.go
Outdated
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'd prefer it if we kept this around, but set it to the runtime's DetachKeys instead of hard-coding C-p C-q. That way, we don't have to unconditionally pass the keys in as part of StartAndAttach() - we get the defaults if not overridden.
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'm not sure how can I retrieve the runtime DetachKeys here without making an import loop
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.
Pass then in as a separate argument, I think (keys, defaultKeys []byte)
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.
Alternatively, push determining the keys up the stack into attachContainerSocket(), which has a runtime available to get the keys
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.
Get the default keys, rather
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 preferred moving the choice in attachContainerSocket, so that term.ToBytes can be called only once.
|
/ok-to-test |
docs/podman-run.1.md
Outdated
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'm not a fan of the word "You" in a man page. Can you drop it and just cap "Configure"
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 can drop this "You", note however that there are other "You" around in the doc.
|
this will need to also be implemented for the remote-client as well ... more specifically, reading from its conf file. |
d1042b1 to
a5ec7f9
Compare
|
I have pushed one more commit to fix a bug found while testing these changes: when starting with attach (using |
a5ec7f9 to
79d1c6c
Compare
|
Prow failures look like infra flakes |
|
Code LGTM |
79d1c6c to
263ae52
Compare
|
☔ The latest upstream changes (presumably #3419) made this pull request unmergeable. Please resolve the merge conflicts. |
Add the ability of specifying a detach keys sequence in libpod.conf Signed-off-by: Marco Vedovati <mvedovati@suse.com>
Signed-off-by: Marco Vedovati <mvedovati@suse.com>
When a container is attached upon start, the WaitGroup counter may never be decremented if an error is raised before start, causing the caller to hang. Synchronize with the start & attach goroutine using a channel, to be able to detect failures before start. Signed-off-by: Marco Vedovati <mvedovati@suse.com>
263ae52 to
4f56964
Compare
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: marcov, mheon The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
@mheon @TomSweeneyRedHat, I updated and rebased this PR based on your reviews, let me know if you expect something else to be changed/added. |
|
Sorry for the delay here. |
Add the ability of specifying a detach keys sequence in libpod.conf
Signed-off-by: Marco Vedovati mvedovati@suse.com