toolshed/docker-cli
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
11,058 Commits 3 Branches 295 Tags
eda4d7b0de5ff6181ca3edaf812c2d7cb92cc3ff
Commit Graph

6 Commits

Author SHA1 Message Date
Samuel PHAN
974ae2755d Update docker-attach.1.md 
Upstream-commit: 5073554ca67f7f1f3f21d87cab766708556486c2
Component: engine
 2014-08-14 14:20:38 +02:00
Matthew Heon
638498458f Update docs on --sig-proxy to indicate that SIGKILL and SIGSTOP cannot be proxied 
Docker-DCO-1.1-Signed-off-by: Matt Heon <mheon@redhat.com> (github: mheon)
Upstream-commit: 31351d08a35b2c903a2b6407bea09ccf1449e79c
Component: engine
 2014-07-18 12:32:04 -04:00
SvenDowideit
c8806a50df I'm going to wish I didn't do this 
Docker-DCO-1.1-Signed-off-by: SvenDowideit <SvenDowideit@home.org.au> (github: SvenDowideit)
Upstream-commit: fa29b1f062d25c1a8ca62f02b9cc7533df4c7449
Component: engine
 2014-07-03 10:31:56 +10:00
SvenDowideit
bedc0093af Update cli.md and man pages to match current cli 
Docker-DCO-1.1-Signed-off-by: SvenDowideit <SvenDowideit@home.org.au> (github: SvenDowideit)
Upstream-commit: b07f193822d00e40580cd11320ed7e01b629f9d7
Component: engine
 2014-07-03 10:22:20 +10:00
Matthew Heon
a8f5e76a89 Update documentation noting that SIGCHLD is not proxied. 
Docker's --sig-proxy option sends all signals but one to a container. The
exception s SIGCHLD, which is deliberately ignored as it doesn't make sense to
send such a signal to a process in a container. Documentation updates will make
this less confusing if anyone does attempt to do this.

Docker-DCO-1.1-Signed-off-by: Matt Heon <mheon@redhat.com> (github: mheon)
Upstream-commit: be4f4599a6d2a517e615dc1f64527a3f2ad2f683
Component: engine
 2014-06-25 09:08:02 -04:00
SvenDowideit
b873d0d1bc move the man pages to the docs/ dir 
Docker-DCO-1.1-Signed-off-by: SvenDowideit <SvenDowideit@home.org.au> (github: SvenDowideit)
Upstream-commit: 42be6f2957c945e070079ec773e29b356a9f9452
Component: engine
 2014-06-24 13:07:42 +10:00