RUN <process> can leave processes running in the background
#247
Assignees
Labels
kind/bug
Something isn't working
Comments
|
Yeah we should definitely fix this one. I think we'll need to use the process group technique. |
balopat
added a commit
to balopat/kaniko
that referenced
this issue
Jul 26, 2018
balopat
added a commit
to balopat/kaniko
that referenced
this issue
Jul 26, 2018
balopat
added a commit
to balopat/kaniko
that referenced
this issue
Jul 26, 2018
4 tasks
imjasonh
added a commit
to imjasonh/catalog
that referenced
this issue
Mar 10, 2021
- use newer jq image built by imega - explicitly list capabilities kaniko should have, including KILL to stop background processes (see GoogleContainerTools/kaniko#247)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Some
RUNinstructions on Dockerfiles can leave processes running in the background (e.g. daemons). If these daemons are writting to files in the context dir,tarwill fail with:... when the layer is being snapshotted, because files were modified after the tar header was written.
One idea to prevent this is to execute
RUNinstructions in a nested PID namespace, andkill -9its PID 1 before proceeding to the next instruction. Or perhaps a poor man's version of it with process groups to minimize the problem on environments that can'tunsharea nested PID namespace.It is easy to reproduce this when building Dockerfiles that use
gradlew, which spawns a daemon by default, and is constantly writting to a log file inside the layer.The text was updated successfully, but these errors were encountered: