-
Bug
-
Resolution: Fixed
-
Major
-
None
-
Linux(CentOS 7)
Jenkins image: jenkins/jenkins:lts, version: v2.414.2, jnlp image jenkins/inbound-agent:alpine
JDK version: openjdk version "11.0.20.1"
experiment one:
I added a container named jnlp in the Container Template under the kubernetes function module, as well as other containers I need. After running the job, all the containers in the pod started normally. However, the pipeline task would not be executed and was always in deactivation. machine status.
--------------------------------------------------------------------------------------------
Experiment 2:
I put the jnlp image in the JNLP Docker Registry input box. At this time, the jnlp container will not be started and an error message will appear.
----------------------------------------------------------------------------------
Experiment three:
I can run it successfully without specifying any jnlp image address, and the name of the custom container cannot be called jnlp, otherwise there will be problems.