Restarting an "auto" container

[ggjulio]

When I run docker run docker-OSX:auto. Everything is fine, I have an interactive shell
But when I restart, I should connect myself using ssh from another terminal.
Is it normal ? If yes, maybe update the readme to precise it ?

➜  ~ docker run -it  --device /dev/kvm -p 50922:10022 -e TERMS_OF_USE=i_agree sickcodes/docker-osx:auto
$> exit
➜  ~ docker start -i objective_kalam
By using this Dockerfile, you hereby agree that you are a security reseacher or developer and agree to use this Dockerfile to make the world a safer place. Examples include: making your apps safer, finding your mobile phone, compiling security products, etc. You understand that Docker-OSX is an Open Source project, which is released to the public under the GNU Pulic License version 3 and above. You acknowledge that the Open Source project is absolutely unaffiliated with any third party, in any form whatsoever. Any trademarks or intelectual property which happen to be mentioned anywhere in or around the project are owned by their respective owners. By using this Dockerfile, you agree to agree to the EULA of each piece of upstream or downstream software. The following code is released for the sole purpose of security research, under the GNU Public License version 3. If you are concerned about the licensing, please note that this project is not AGPL. A copy of the license is available online: https://github.com/sickcodes/Docker-OSX/blob/master/LICENSE. In order to use the following Dockerfile you must read and understand the terms. Once you have read the terms, use the -e TERMS_OF_USE=i_agree or -e TERMS_OF_USE=i_disagree
Disk is being copied between layers... Please wait a minute...
touch: cannot touch '': No such file or directory
chown: cannot access '': No such file or directory
nohup: appending output to 'nohup.out'

# no interactive shell here
# So I ssl connect myself from another terminal
➜  ~ ssh user@localhost -p 50922
$>

[ggjulio]

Well, I just noticed docker start need to be attached explicitly. (at least for command line only)
Maybe update the readme ?

docker start -ai container_id

[sickcodes]

Oh this is a great find! Does this drop you back into the shell?

[ggjulio]

Yes back into the shell.

[sickcodes]

Thanks! Added 37ed54d

[ggjulio]

To be exact at this line, stdin is attached by -i. And -a attach out/err + signals.

man docker start
--attach       -a  -- Attach container's stdout/stderr and forward all signals
--interactive  -i  -- Attach container's stdin

Edit:
Well docker run has a different definition than docker start

man docker run
--attach                 -a  -- Attach to stdin, stdout or stderr                                                  
--interactive            -i  -- Keep stdin open even if not attached

Anyway.
Thank for this really useful repository.