Skip to content
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

podman attach/exec do not respect "detach_keys" configuration while podman run does #4556

Closed
cjao opened this issue Nov 22, 2019 · 3 comments · Fixed by #4651
Closed

podman attach/exec do not respect "detach_keys" configuration while podman run does #4556

cjao opened this issue Nov 22, 2019 · 3 comments · Fixed by #4651
Assignees
Labels
kind/bug Categorizes issue or PR as related to a bug. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments.

Comments

@cjao
Copy link

cjao commented Nov 22, 2019

Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)

/kind bug

Description

I'm trying to work around bug #4208 temporarily by setting "detach_keys" in .config/containers/libpod.conf to another sequence like "ctrl-q,ctrl-q" (ctrl-q being less of a problem in emacs or bash). This indeed works for interactive containers created by podman run -ti. However, when I enter that container from another terminal window through podman attach or podman exec, the detach-keys sequence still seems hardcoded to "ctrl-p,ctrl-q".

Steps to reproduce the issue:

  1. Set detach_keys = "ctrl-q,ctrl-q" in .config/containers/libpod.conf

  2. Confirm that ctrl-q,ctrl-q detaches from the container started by podman run --rm -it fedora-toolbox:31 bash (or another image),

  3. Start another container using podman create, such as podman create --name ctr --rm -it fedora-toolbox:31 bash && podman start ctr && podman attach ctr, and check that ctrl-p,ctrl-q is still its detach sequence.

Output of podman version:

Version:            1.6.2
RemoteAPI Version:  1
Go Version:         go1.13.1
OS/Arch:            linux/amd64

Output of podman info --debug:

debug:
  compiler: gc
  git commit: ""
  go version: go1.13.1
  podman version: 1.6.2
host:
  BuildahVersion: 1.11.3
  CgroupVersion: v2
  Conmon:
    package: conmon-2.0.2-1.fc31.x86_64
    path: /usr/bin/conmon
    version: 'conmon version 2.0.2, commit: 186a550ba0866ce799d74006dab97969a2107979'
  Distribution:
    distribution: fedora
    version: "31"
  IDMappings:
    gidmap:
    - container_id: 0
      host_id: 1000
      size: 1
    - container_id: 1
      host_id: 100000
      size: 65536
    uidmap:
    - container_id: 0
      host_id: 1000
      size: 1
    - container_id: 1
      host_id: 100000
      size: 65536
  MemFree: 5513392128
  MemTotal: 12431245312
  OCIRuntime:
    name: crun
    package: crun-0.10.6-1.fc31.x86_64
    path: /usr/bin/crun
    version: |-
      crun version 0.10.6
      spec: 1.0.0
      +SYSTEMD +SELINUX +APPARMOR +CAP +SECCOMP +EBPF +YAJL
  SwapFree: 6299840512
  SwapTotal: 6299840512
  arch: amd64
  cpus: 4
  eventlogger: journald
  hostname: localhost.localdomain
  kernel: 5.3.11-300.fc31.x86_64
  os: linux
  rootless: true
  slirp4netns:
    Executable: /usr/bin/slirp4netns
    Package: slirp4netns-0.4.0-20.1.dev.gitbbd6f25.fc31.x86_64
    Version: |-
      slirp4netns version 0.4.0-beta.3+dev
      commit: bbd6f25c70d5db2a1cd3bfb0416a8db99a75ed7e
  uptime: 4h 17m 5.13s (Approximately 0.17 days)
registries:
  blocked: null
  insecure: null
  search:
  - docker.io
  - registry.fedoraproject.org
  - registry.access.redhat.com
  - registry.centos.org
  - quay.io
store:
  ConfigFile: /var/home/casey/.config/containers/storage.conf
  ContainerStore:
    number: 1
  GraphDriverName: overlay
  GraphOptions:
    overlay.mount_program:
      Executable: /usr/bin/fuse-overlayfs
      Package: fuse-overlayfs-0.7-1.fc31.x86_64
      Version: |-
        fusermount3 version: 3.6.2
        fuse-overlayfs: version 0.7
        FUSE library version 3.6.2
        using FUSE kernel interface version 7.29
  GraphRoot: /var/home/casey/.local/share/containers/storage
  GraphStatus:
    Backing Filesystem: extfs
    Native Overlay Diff: "false"
    Supports d_type: "true"
    Using metacopy: "false"
  ImageStore:
    number: 2
  RunRoot: /run/user/1000
  VolumePath: /var/home/casey/.local/share/containers/storage/volumes

Package info (e.g. output of rpm -q podman or apt list podman):

podman-1.6.2-2.fc31.x86_64
@openshift-ci-robot openshift-ci-robot added the kind/bug Categorizes issue or PR as related to a bug. label Nov 22, 2019
@cjao cjao changed the title podman create does not respect "detach_keys" configuration while podman run does podman attach/exec do not respect "detach_keys" configuration while podman run does Nov 23, 2019
@marcov
Copy link
Collaborator

marcov commented Nov 28, 2019

This is a regression of #4441

@rhatdan
Copy link
Member

rhatdan commented Nov 29, 2019

@marcov Any interest in opening a PR to fix?

@marcov
Copy link
Collaborator

marcov commented Nov 29, 2019

Sure, I'll follow up soon!

@marcov marcov self-assigned this Nov 29, 2019
marcov added a commit to marcov/libpod that referenced this issue Dec 5, 2019
Fixes: containers#4556

Signed-off-by: Marco Vedovati <mv@sba.lat>
marcov added a commit to marcov/libpod that referenced this issue Dec 5, 2019
Fixes: containers#4556

Signed-off-by: Marco Vedovati <mv@sba.lat>
marcov added a commit to marcov/libpod that referenced this issue Dec 5, 2019
Fixes: containers#4556

Signed-off-by: Marco Vedovati <mv@sba.lat>
marcov added a commit to marcov/libpod that referenced this issue Dec 6, 2019
Fixes: containers#4556

Signed-off-by: Marco Vedovati <mv@sba.lat>
@github-actions github-actions bot added the locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. label Sep 23, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 23, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
kind/bug Categorizes issue or PR as related to a bug. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants