why docker not executing init as lxc

Question

Docker is not running init. So services are not started during startup. Lxc runs init during lxc-start.Since Docker is using lxc why it is not running init. What are the advantages of not running init and depending on supervisord for daemonization?

score 1 · Answer 1 · edited May 23 '17 at 11:33

1

This question has been raised as an issue on GitHub, and a pull request merged to allow init to be run since 0.6.x):

docker run $IMAGE /sbin/init

source

The original reason init wasn't run (not valid since 0.6.x):

when starting a new container, docker mint-bounds itself as /sbin/init inside the container, hiding the real /sbin/init and in the proces smaking it unavailable for execution.

This answer may offer more help, and The Docker Guidebook may come in handy.

edited May 23 '17 at 11:33

Community

1

answered Dec 19 '13 at 13:32

Andy

5,230
1
24
34

I dont think it is fixed. Iam using 0.7.1 docker. Still facing it. Init says /com/ubuntu/upstart sock not found. – kalyan Dec 19 '13 at 14:15
How are you invoking docker/init? – Andy Dec 19 '13 at 17:08
docker run ubuntu /sbin/init – kalyan Dec 19 '13 at 20:37

score 1 · Accepted Answer · answered Dec 28 '15 at 02:19

Docker is an application container, more focused in distribute apps as containers. In this the app/process running inside the container is the only one running, their init process. If your process need more apps (mysql, mongodb database, etc.) you don't launch these inside your docker container managed by one init daemon, you launch more docker containers, every one inside the docker container.

You can try http://phusion.github.io/baseimage-docker/ that provides a simple init daemon to run more process inside your docker image (this one is Ubuntu based) or you can try LXD http://www.ubuntu.com/cloud/lxd for container technology used more like a system container.

why docker not executing init as lxc

2 Answers2