p4u1/docker-cli
0
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
28,307 Commits 2 Branches 295 Tags
9cb45952e04746ea0ec7c19ec1e2e2ac4eefd986
Commit Graph

12 Commits

Author SHA1 Message Date
allencloud
ba822f35dd make more pkgs support darwin 
Signed-off-by: allencloud <allen.sun@daocloud.io>
Upstream-commit: bd11a269bc114334cf6160ba38e396f8f0e3aecd
Component: engine
 2016-08-10 22:56:05 +08:00
Amit Krishnan
3a35464d9d Get the Docker Engine to build clean on Solaris 
Signed-off-by: Amit Krishnan <krish.amit@gmail.com>
Upstream-commit: 86d8758e2bb5e9d21d454ceda90b33feb8e74771
Component: engine
 2016-05-23 16:37:12 -07:00
allencloud
f4582c23f4 fix typos in pkg 
Signed-off-by: allencloud <allen.sun@daocloud.io>
Upstream-commit: aef02273d9cdf8144b95c9c9a8d1e119d24b2d9d
Component: engine
 2016-04-09 21:18:15 +08:00
Justas Brazauskas
3c4fcf6b7a Fix typos found across repository 
Signed-off-by: Justas Brazauskas <brazauskasjustas@gmail.com>
Upstream-commit: 927b334ebfc786276a039e45ec097e71bf9a104c
Component: engine
 2015-12-13 18:04:12 +02:00
Alexey Guskov
59df5a01ec make docker compile on freebsd 
Signed-off-by: Alexey Guskov <lexag@mail.ru>
Upstream-commit: 26c03d561ab126287bb3034cc23477d18869a888
Component: engine
 2015-07-29 21:25:56 +03:00
Tibor Vass
d7e24680cc reexec: Use in-memory binary on linux instead of os.Args[0] 
This keeps reexec working properly even if the on-disk binary was replaced.

Signed-off-by: Tibor Vass <tibor@docker.com>
Upstream-commit: 5aee8807a67687941916fc85c6d4da6bc59e834b
Component: engine
 2015-07-24 14:15:50 -04:00
Alexander Morozov
2f038465a8 Add docstring to reexec.Command 
Signed-off-by: Alexander Morozov <lk4d4@docker.com>
Upstream-commit: 9738b9319b7a5133653c4912db8ec361af5847fc
Component: engine
 2015-07-20 17:00:18 -07:00
John Howard
c39c5e2a47 Windows: reexec pkg supported 
Signed-off-by: John Howard <jhoward@microsoft.com>
Upstream-commit: 64715c4f33fdb98003b7fda8d1dcf9c65463de07
Component: engine
 2015-05-08 14:15:53 -07:00
Phil Estes
7741ef02eb Fix relative path execution of docker daemon in reexec.Self() 
After the new libcontainer API, the reexec.Self() output of the daemon
binary is used as the libcontainer factory InitPath.  If it is relative,
it can't be found at container start time.  This patch solves the
problem by making sure that we return a rooted/absolute path if a
relative path is used.

Docker-DCO-1.1-Signed-off-by: Phil Estes <estesp@linux.vnet.ibm.com> (github: estesp)
Upstream-commit: 334aea3441d9e499b7f999098a16abcb81d16a68
Component: engine
 2015-03-16 16:52:00 -04:00
Arnaud Porterie
5506a9a27c Remove subdirectories MAINTAINERS files 
Signed-off-by: Arnaud Porterie <arnaud.porterie@docker.com>
Upstream-commit: 89bdaa35e04b74b7c6528783e0f7b8154b2a3d31
Component: engine
 2015-03-06 18:21:51 -08:00
unclejack
dd4a9e5429 add pkg/chrootarchive and use it on the daemon 
Docker-DCO-1.1-Signed-off-by: Cristian Staretu <cristian.staretu@gmail.com> (github: unclejack)

Conflicts:
	builder/internals.go
	daemon/graphdriver/aufs/aufs.go
	daemon/volumes.go
		fixed conflicts in imports
Upstream-commit: 1cb17f03d0b217acf2d2c289b4946d367f9d3e80
Component: engine
 2014-11-25 01:03:40 +02:00
unclejack
3dbfc4607d pkg/reexec: move reexec code to a new package 
Docker-DCO-1.1-Signed-off-by: Cristian Staretu <cristian.staretu@gmail.com> (github: unclejack)
Upstream-commit: acd64278f13ef0ee565f4819951393b9c3fe89eb
Component: engine
 2014-10-30 14:48:30 +02:00