11–16 of 16 posts
Source: `docker pull jbergstroem/mariadb-alpine`
edit: docker should really open the doors for a cleanup/shutdown phase. There's both entrypoint and cmd but not a "exit" command.
# Run with care...
$ sudo docker run -it docker.io/ubuntu:14.04 /bin/bash -c 'trap x EXIT; x() { echo exit; }; while sleep 1; do echo sleep; done'
^C
[bash enter in infinite loop]
I'm asking because my Fedora 25 install does not include docker 1.13 yet.
I was relieved to see the article mention dumb-init in its conclusion. It's very likely what you want if you're not booting your containers with a full init system, and the README has a thorough explanation of why and how dumb-init works. https://github.com/Yelp/dumb-init
Lately I've found myself using runit a lot in docker containers. In the happy path with a single process, you still gain because it does leave you a bunch of nice hooks when docker exec'ing to shutdown/restart your main process when your developing. In the more common path, I rarely have containers which don't more easily share 1 or 2 tightly coupled support containers (and in general I prefer having `docker run` jus…
What is meant by "the happy path"? I've seen this reference a couple of time now but have not found a clear explanation.
Earlier quoted context omitted.
Lately I've found myself using runit a lot in docker containers. In the happy path with a single process, you still gain because it does leave you a bunch of nice hooks when docker exec'ing to shutdown/restart your main process when your developing. In the more common path, I rarely have containers which don't more easily share 1 or 2 tightly coupled support containers (and in general I prefer having `docker run` jus…
>"In the happy path with a single process ..." What is meant by "the happy path"? I've seen this reference a couple of time now but have not found a clear explanation.
I wonder if using the --init flag would also fix the docker issue with bash scripts getting in an infinite loop when the script catch signals: # Run with care... $ sudo docker run -it docker.io/ubuntu:14.04 /bin/bash -c 'trap x EXIT; x() { echo exit; }; while sleep 1; do echo sleep; done' ^C [bash enter in infinite loop] I'm asking because my Fedora 25 install does not include docker 1.13 yet.
[0] https://docs.docker.com/engine/installation/linux/docker-ce/...
Noticed the same thing when running a node.js application in docker a while ago. Adding a signal handler manually fixed it easily. It was just not expected to be necessary.