-
Bug
-
Resolution: Unresolved
-
Minor
When Image.Inside() or an "agent { docker ... }" is used to docker run ... cat a docker container, it should always use the --init flag.
--init Run an init inside the container that forwards signals and reaps processes
This creates a PID 1 --init process that is sometimes needed to properly shutdown a container with multiple processes inside it.
A lot of build containers can start up a bunch of processes that may not be properly reaped or may not properly receive TERM and QUIT signals when trying to shutdown a container.
This should fix problems like JENKINS-37769 and JENKINS-32859
- is related to
-
-
- Open
-
-
JENKINS-37769 Too long stop docker container(default docker stop timeout=10s)
-
- Resolved
-
[JENKINS-45888] Image.inside and Agent should use --init with 'docker run'
| Link |
New:
This issue is related to |
| Link | New: This issue is related to JENKINS-32859 [ JENKINS-32859 ] |
| Description |
Original:
When {{Image.Inside()}} or an "agent \{ docker ... }" is used to {{docker run ... cat}} a docker container, it should always use the {{--init}} flag. {noformat} --init Run an init inside the container that forwards signals and reaps processes{noformat} This creates a PID 1{{init}} process that is sometimes needed to properly shutdown a container with multiple processes inside it. A lot of build containers can start up a bunch of processes that may not be properly reaped or may not properly receive {{TERM}} and {{QUIT}} signals when trying to shutdown a container. This should fix problems like |
New:
When {{Image.Inside()}} or an "agent \{ docker ... }" is used to {{docker run ... cat}} a docker container, it should always use the {{--init}} flag. {noformat} --init Run an init inside the container that forwards signals and reaps processes{noformat} This creates a PID 1 {{--init}} process that is sometimes needed to properly shutdown a container with multiple processes inside it. A lot of build containers can start up a bunch of processes that may not be properly reaped or may not properly receive {{TERM}} and {{QUIT}} signals when trying to shutdown a container. This should fix problems like |