- testing 4.3.1+ds1-6+b2
- unstable 4.3.1+ds1-8+b1
- experimental 4.4.0+ds1-1
podman-attach(1)() | podman-attach(1)() |
NAME¶
podman-attach - Attach to a running container
SYNOPSIS¶
podman attach [options] container
podman container attach [options] container
DESCRIPTION¶
The attach command allows you to attach to a running container using the container's ID or name, either to view its ongoing output or to control it interactively.
You can detach from the container (and leave it running) using a configurable key sequence. The default sequence is ctrl-p,ctrl-q. Configure the keys sequence using the --detach-keys option, or specifying it in the containers.conf file: see containers.conf(5) for more information.
OPTIONS¶
--detach-keys=sequence¶
Specify the key sequence for detaching a container. Format is a single character [a-Z] or one or more ctrl-<value> characters where <value> is one of: a-z, @, ^, [, , or _. Specifying "" will disable this feature. The default is ctrl-p,ctrl-q.
--latest, -l¶
Instead of providing the container name or ID, use the last created container. If you use methods other than Podman to run containers such as CRI-O, the last started container could be from either of those methods.
The latest option is not supported on the remote client.
--no-stdin¶
Do not attach STDIN. The default is false.
--sig-proxy=true|false¶
Proxy received signals to the process (non-TTY mode only). SIGCHLD, SIGSTOP, and SIGKILL are not proxied. The default is true.
EXAMPLES¶
$ podman attach foobar [root@localhost /]#
$ podman attach --latest [root@localhost /]#
$ podman attach 1234 [root@localhost /]#
$ podman attach --no-stdin foobar
SEE ALSO¶
podman(1), podman-exec(1), podman-run(1), containers.conf(5)