Docker attach: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
Line 5: Line 5:
=Overview=
=Overview=


Attach local standard input, output, and error streams to a running container. The container to attach to should be started in [[Docker_run#-i.2C_--interactive|interactive mode]], giving the ability to type into it, and with a [[Docker_run#-t.2C_--tty|TTY]] so you can see the input and output:
Attaches the invoking shell's stdin, stdout and stderr to the container specified as argument. Attachment will only succeed if the target container was started in interactive mode. The container to attach to should be started in [[Docker_run#-i.2C_--interactive|interactive mode]], giving the ability to type into it, and with a [[Docker_run#-t.2C_--tty|TTY]] so you can see the input and output:


  docker run -dit alpine1 alpine ash
  docker run [-d] -i alpine1 alpine ash


Then, the attachment can be performed later:
Then, the attachment can be performed later:


  docker attach alpine1
  docker attach alpine1

Revision as of 07:38, 3 May 2018

Internal

Overview

Attaches the invoking shell's stdin, stdout and stderr to the container specified as argument. Attachment will only succeed if the target container was started in interactive mode. The container to attach to should be started in interactive mode, giving the ability to type into it, and with a TTY so you can see the input and output:

docker run [-d] -i alpine1 alpine ash

Then, the attachment can be performed later:

docker attach alpine1