-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
Jenkins version : Jenkins 2.249.1
Durable task : 1.35
I am using jenkins version : Jenkins 2.249.1
Durable task : 1.35
We run builds in kubenetes farm and our builds are dockerised, After the upgrade of Jenkins, and durable plugins as we see multiple issues raised with "sh" initialisation inside the container breaks, we considered the above solution as suggested and set workingDir: "/home/jenkins/agent" and builds are success after making the change.
How ever still some of the builds on Jenkins are still failing randomly with same error
[2021-05-10T15:16:33.046Z] [Pipeline] sh [2021-05-10T15:22:08.073Z] process apparently never started in /home/jenkins/agent/workspace/CORE-CommitStage@tmp/durable-f6a728e7 [2021-05-10T15:22:08.087Z] [Pipeline] }
Also we had already enabled as per suggestions-
-Dorg.jenkinsci.plugins.durabletask.BourneShellScript.LAUNCH_DIAGNOSTICS=true \
Issue is however not persistent but still jobs fails randomly. Looking for permanent fix for the current issue.
- relates to
-
JENKINS-64608 Detection "running inside container" fails with cgroup namespace "private" for docker daemon
-
- Resolved
-
carroll Thanks for getting back to me.
FORCE_BINARY_WRAPPER did not really add that much information, at least nothing looking like a stacktrace. The log shows the following message repeated about every minute
Then, finally we see the following when the job exits (with the error message):
Is this normal? Especially the part that the first code-block is printed at every minute.