moby--moby/pkg/reexec/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.
First header should be a top level header Signed-off-by: yupeng <yu.peng36@zte.com.cn> 2016-11-21 09:08:28 +00:00			`# reexec`
Use argv0 as reexec implementation for dockerinit This changes the way the exec drivers work by not specifing a -driver flag on reexec. For each of the exec drivers they register their own functions that will be matched aginst the argv 0 on exec and called if they match. This also allows any functionality to be added to docker so that the binary can be reexec'd and any type of function can be called. I moved the flag parsing on docker exec to the specific initializers so that the implementations do not bleed into one another. This also allows for more flexability within reexec initializers to specify their own flags and options. Signed-off-by: Michael Crosby <michael@docker.com> 2014-08-08 20:18:18 +00:00
			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.`