10324 2016-09-22 20:21:09 +0000 When running builds in a docker contain, they occasionally fail and close the container 2016-09-29 14:35:57 +0000 1 1 7 Build System, Metadata & Runtime OE-Core Scripts and Tools 2.2 x86 Multiple RESOLVED FIXED Undecided normal 2.2 M4 1 mark.hatle mark.hatle hongxu.jia joshuagloe mark.asselstine richard.purdie ross.burton seebs --- --- No (bug/feature does not impact docs) oldest_to_newest 66518 0 mark.hatle 2016-09-22 20:21:09 +0000 It was discovered that in some cases a build in a docker container would cause the container to terminate. It appeared that the mini init program in the container would simply exist. In a heavily loaded container, the child process might not started before the parent process had terminated. The child process attempts to signal the parent with SIGUSR1. If the parent had terminated, the parent becomes PID 1, which is generally init. When it signaled pid 1, it caused the docker mini-init to terminate. This doesn't happen in a traditional system, as systemd/sysvinit is protected to only root users can signal it. This was fixed in the pseudo commit: 647ea4b1bc780b40a852e7e2d1439f700339e613 66551 1 mark.hatle 2016-09-23 14:57:56 +0000 Sent to oe-core list on 2016-09-22 66713 2 richard.purdie 2016-09-29 14:35:57 +0000 http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=2305c0038dd7d9d3bffd7babdffc81deafbe45a1