Container jnlp was terminated (Exit Code: 1, Reason: Error) #600
Comments
|
We are experiencing this issue too with inbound-agent:latest. We have downgraded inbound-agent to version 4.10-3-jdk11 to avoid this problem. |
|
could you attach a full log please? I would also recommend you don't use the latest tag and instead use a specific version. e.g. |
|
We have tried different version and getting the same issue Please find the logs below Pipeline logs: 16:25:43 [Pipeline] Start of Pipeline Jenkins logs: |
|
|
Hi @dduportal root@jenkins-78399b5weq:/# java -version |
|
@kkavin While I'm trying to reproduce the error with a local k3s cluster, could you retrieve the agent pod's logs and description? |
|
This is most likely a problem with clouds that use a restrictive user model (such as OpenShift). One of my colleagues looked into this and found that the problem could be related to this change https://github.com/jenkinsci/docker-agent/blame/master/11/alpine/Dockerfile#L42 introduced quite recently. The problem has also been introduced for other Debian og Archlinux images. 4.10-3-jdk11 (works): latest (not working): |
Good catch, thanks! Gotta publish a fix today |
|
First step for fixing: #333 (then, release of |
|
Thanks @peterwvj @kkavin , can you retry with the latest image (https://github.com/jenkinsci/docker-inbound-agent/releases/tag/3077.vd69cf116da_6f-2) ? |
|
@dduportal thanks for looking into this. I will try out the new image tomorrow when I'm back at work and get back to you. |
|
@dduportal Yes it works fine with the below mentioned images. But getting error while using jenkins/inbound-agent:alpine Working images |
@kkavin thanks for the feedback. Can you share with us the digests of the images? I can't see any differences between Their digest should be the same: $ docker pull jenkins/inbound-agent:alpine
alpine: Pulling from jenkins/inbound-agent
ca7dd9ec2225: Already exists
bb9822f87bb1: Already exists
1ec5de7441ae: Already exists
da0dd61568d7: Already exists
1b5946bf4ab8: Pull complete
ae36e3c04603: Pull complete
910ecf5df8fc: Pull complete
438a880a5d43: Pull complete
e46780d55c94: Pull complete
4f4fb700ef54: Pull complete
aa9b5a50e6c1: Pull complete
8ddadee1da24: Pull complete
Digest: sha256:bf476e43de493f0bc1bf2030cc4da53b387e984e5239a2b3898862b9733a5dc7
Status: Downloaded newer image for jenkins/inbound-agent:alpine
docker.io/jenkins/inbound-agent:alpine
$ docker pull jenkins/inbound-agent:alpine-jdk11
alpine-jdk11: Pulling from jenkins/inbound-agent
Digest: sha256:bf476e43de493f0bc1bf2030cc4da53b387e984e5239a2b3898862b9733a5dc7
Status: Downloaded newer image for jenkins/inbound-agent:alpine-jdk11
docker.io/jenkins/inbound-agent:alpine-jdk11 |
|
@dduportal 3077.vd69cf116da_6f-2 and latest now work for me. Thanks again. |
|
@dduportal After pulling the docker image the pipeline is working fine. Thanks for fixing the issue @dduportal |
|
Closing the issue as confirmed by users. Thanks a lot |
…ye (#307) Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
…inbound-agent/gh-307 fix(linux) ensure that users different than jenkins and root are allowed to start agent process
Jenkins and plugins versions report
Environment
What Operating System are you using (both controller, and any agents involved in the problem)?
Kubernetes Worker nodes with Amazon linux
with agents:
Reproduction steps
Step -1 : Created pipeline with the yaml configuration
containers:
- name: jnlp
image: jenkins/inbound-agent:alpine
securityContext:
runAsUser: 1001
runAsUser: 1001
Step -2 : Running the pipline
Expected Results
Jnlp image creation successful
Actual Results
Pipeline failed with the below error
**Container jnlp was terminated (Exit Code: 1, Reason: Error)
jnlp -- terminated (1)
Error: Could not find or load main class hudson.remoting.jnlp.Main
Caused by: java.lang.ClassNotFoundException: hudson.remoting.jnlp.Main**
Anything else?
After updating to this new image all the pipelines are getting failed
The text was updated successfully, but these errors were encountered: