Ubuntu
runit package

  1. Bug #1371290
  2. Activity log

Activity log for bug #1371290

Date Who What changed Old value New value Message
2014-09-18 19:56:03 Trevor Joynson bug added bug
2014-09-18 20:27:29 Trevor Joynson description In runit.postinit, kill -s HUP 1 is executed. This is an issue in the case of a docker container where you are running bash as PID 1. When bash is send HUP, it will exit instantly, making installation of runit impossible without overriding the kill command. In runit.postinit, kill -s HUP 1 is executed. This is an issue in the case of a docker container where you are running bash as PID 1. When bash is sent HUP, it will exit instantly, making installation of runit impossible without overriding the kill command. As a workaround I've made my container have an entrypoint of a bash script that does 'trap ":" HUP' but that's quite a hack to me.
2014-09-18 20:27:49 Trevor Joynson description In runit.postinit, kill -s HUP 1 is executed. This is an issue in the case of a docker container where you are running bash as PID 1. When bash is sent HUP, it will exit instantly, making installation of runit impossible without overriding the kill command. As a workaround I've made my container have an entrypoint of a bash script that does 'trap ":" HUP' but that's quite a hack to me. In runit.postinit, kill -s HUP 1 is executed. This is an issue in the case of a docker container where you are running bash as PID 1. When bash is sent HUP, it will exit instantly, making installation of runit impossible. As a workaround I've made my container have an entrypoint of a bash script that does 'trap ":" HUP' but that's quite a hack to me.
2014-09-18 20:28:23 Trevor Joynson description In runit.postinit, kill -s HUP 1 is executed. This is an issue in the case of a docker container where you are running bash as PID 1. When bash is sent HUP, it will exit instantly, making installation of runit impossible. As a workaround I've made my container have an entrypoint of a bash script that does 'trap ":" HUP' but that's quite a hack to me. In runit.postinit, kill -s HUP 1 is executed. This is an issue in the case of a docker container where you are running bash as PID 1. When bash is sent HUP, it will exit, making installation of runit impossible. As a workaround I've made my container have an entrypoint of a bash script that does 'trap ":" HUP' but that's quite a hack to me.