docker-cli

Files

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

command_linux.go

add pkg/chrootarchive and use it on the daemon

2014-11-25 01:03:40 +02:00

command_unsupported.go

add pkg/chrootarchive and use it on the daemon

2014-11-25 01:03:40 +02:00

README.md

pkg/reexec: move reexec code to a new package

2014-10-30 14:48:30 +02:00

reexec.go

Fix relative path execution of docker daemon in reexec.Self()

2015-03-16 16:52:00 -04:00

README.md

reexec

The reexec package facilitates the busybox style reexec of the docker binary that we require because of the forking limitations of using Go. Handlers can be registered with a name and the argv 0 of the exec of the binary will be used to find and execute custom init paths.