Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

The process docker runs in the container can be /sbin/init, which spawns an entire OS. Its just not how its normally used.


Correct me if I'm wrong, but as far as I know Docker actually does run a binary called /sbin/init, it's just that they've replaced it in the base images with something that is more suited for fast startup times and running of a single process. Setting the Docker start command to init will probably not accomplish what you want.


That was true in earlier versions of Docker, but has been fixed. alexlarsson is correct :)


Hmm, I guess that could do it. I wonder if I can run the upstart daemon first to have it start my services. That would be ideal.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: