8 Коммитов

Автор	SHA1	Сообщение	Дата
Guillaume J. Charmes	7b0e96f1f4	Manually pass the env to docker-init instead of relying on lxc to pass it	2013-04-16 14:32:50 -07:00
Louis Opter	5e1a975b48	Use ip to setup the gateway in sysinit.go ... ip from iproute2 replaces the legacy route tool which is often not installed by default on recent Linux distributions. The same patch has been done in network.go and is re-used here.	2013-04-10 17:40:28 -07:00
Solomon Hykes	f7eaaa3adb	Clean up 'container' environment variable injected by lxc-start	2013-03-23 19:11:00 -07:00
Solomon Hykes	34fbaa5f6d	'docker run -e': set environment variables in a container	2013-03-22 20:36:34 -07:00
Solomon Hykes	fb350e0c77	Setup a predictable, repeatable environment for containers	2013-03-07 09:25:41 -08:00
Andrea Luzzardi	b9b66d0e1b	sysinit: Support for the -g (gateway) flag used in networking setup	2013-02-21 10:47:57 -08:00
Andrea Luzzardi	6de3e8a22d	Implemented support to run as a different user (through the -u flag)	2013-02-13 17:24:35 -08:00
Andrea Luzzardi	58a2294260	Implemented a self-injecting process wrapper that runs inside the container ... - Before starting the container, docker injects itself inside the container by mount binding the dockerd binary into /sbin/init - Instead of running the user process directly inside the container, we run /sbin/init targetprocess [args...] - When docker is run as /sbin/init (e.g. argv[0] == "/sbin/init"), then its own sys init code kicks in - The sys init code will be responsible for setting up the process environment prior to its execution (setuid, networking, ...). - Finally, docker's sys init will exec() the container's process, thus replacing itself with the target binary (which will be running as pid 1)	2013-02-13 14:01:44 -08:00