C-p is bound over

[her]

kubectl doesn't pass through detach-keys options

for docker --detach-keys ctrl-q,ctrl-q https://docs.docker.com/engine/reference/commandline/attach/#override-the-detach-sequence

This means that C-p is effectively broken in running containers.

[seans3]

/sig cli
/area kubectl

[seans3]

/triage more-information

[k8s-ci-robot]

@seans3: The label(s) triage/more-information cannot be applied, because the repository doesn't have them

In response to this:

/triage more-information

Instructions 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.

[seans3]

/triage needs-information

[her]

@seans3 what type of information are you looking for? Happy to provide.

The basic thing here is that if you shell into a running container managed by kube, readline shortcuts are bound over, like, <C-p>.

Are you familiar with <C-p> in bash?

[eddiezane]

@her do you have a way to reproduce what you're seeing?

I created a deployment with nginx:latest and exec'd in with kubectl exec -it nginx-59d7cd6545-cw87p -- /bin/bash. <C-r> and <C-p> are both working for me.

[her]

I beg you to try again and take a close look. <C-p> is actually the start of the detach sequence in docker.

you can detach from a container and leave it running using the CTRL-p CTRL-q key sequence.

@eddiezane if you run a command in your test container $ echo 'foo' and then issue <C-p> you'll trigger the detach sequence and you won't access entries in history unless you issue the command again (<C-p>).

Indeed, if you issue <C-p> and follow that with <C-q> you'll detach from the container. Docker by default provides a configuration to override the detach sequence but kubectl does not honor it. Override the detach sequence

[eddiezane]

@her ahh got it. Thanks for the explanation!

/remove-triage-needs-information
/priority backlog

[eddiezane]

/remove-triage needs-information