Docker attach: Difference between revisions
Jump to navigation
Jump to search
(Created page with "=Internal= * Docker Client Operations =Overview=") |
No edit summary |
||
| (12 intermediate revisions by the same user not shown) | |||
| Line 4: | Line 4: | ||
=Overview= | =Overview= | ||
Attaches the invoking shell's stdin, stdout and stderr to the container specified as argument. | |||
The attachment will succeed only if the target container was started in [[Docker_Concepts#Interactive_Mode|interactive mode]]: | |||
docker run [-d] '''-i''' alpine ash | |||
Then, the attachment can then be performed with: | |||
docker attach <''container-id''> | |||
Starting the container in [[Docker_Concepts#Detached_Mode|detached mode]] is optional, <tt>docker attach</tt> can attach to a non-detached container as well. In that case, two shells (the one from which [[docker run]] was executed and the one from which [[docker attach#Overview|docker attach]] was executed) will be attached at the same time to the container. | |||
Latest revision as of 07:46, 3 May 2018
Internal
Overview
Attaches the invoking shell's stdin, stdout and stderr to the container specified as argument.
The attachment will succeed only if the target container was started in interactive mode:
docker run [-d] -i alpine ash
Then, the attachment can then be performed with:
docker attach <container-id>
Starting the container in detached mode is optional, docker attach can attach to a non-detached container as well. In that case, two shells (the one from which docker run was executed and the one from which docker attach was executed) will be attached at the same time to the container.