podman/docs/podman-attach.1.md
Daniel J Walsh 99d180efcc Modify man pages so they compile correctly in mandb
This fixes an issue where if you did
man -k podman-run

podman-run (1)    - (unknown subject)

Now you will see

man -k podman-run
podman-run (1)       - Run a command in a new container

More importantly

man -k containers | grep podman
podman (1)           - Simple management tool for containers and images
podman-kill (1)      - Kills one or more containers with a signal
podman-pause (1)     - Pause one or more containers
podman-ps (1)        - Prints out information about containers
podman-rm (1)        - Remove one or more containers
podman-start (1)     - Start one or more containers
podman-stats (1)     - Display a live stream of 1 or more containers' resource usage statistics
podman-stop (1)      - Stop one or more containers
podman-unpause (1)   - Unpause one or more containers
podman-wait (1)      - Waits on one or more containers to stop and prints exit code

Signed-off-by: Daniel J Walsh <dwalsh@redhat.com>

Closes: #676
Approved by: mheon
2018-04-26 13:46:14 +00:00

1.5 KiB

% podman(1) podman-attach - See the output of pid 1 of a container or enter the container % Dan Walsh

podman-attach "1" "December 2017" "podman"

NAME

podman-attach - Attach to a running container

SYNOPSIS

podman 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. You configure the key sequence using the --detach-keys option

OPTIONS

--detach-keys Override the key sequence for detaching a container. Format is a single character [a-Z] or ctrl- where is one of: a-z, @, ^, [, , or _.

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

--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)