Details
-
Type:
Bug
-
Status: Resolved (View Workflow)
-
Priority:
Major
-
Resolution: Fixed
-
Component/s: jenkins-tag-cloud-plugin
-
Labels:
-
Environment:FROM jenkins/jenkins:2.194
-
Similar Issues:
Description
1. jenkins dockerfile version
- jenkins dockerfile version: jenkins/jenkins:2.194
root >> cat /opt/dockerfile/jenkins/02/jenkins-master.Dockerfile
FROM jenkins/jenkins:2.194
MAINTAINER tiandong19860806@126.com
USER root
ENV MAVEN_HOME /usr/local/maven
ENV JAVA_HOME /usr/local/java
ENV M2=/usr/local/maven/repository
ENV CLASSPATH .:$JAVA_HOME/lib:$M2_HOME/lib
ENV PATH $MAVEN_HOME/bin:$JAVA_HOME/bin:$PATH
RUN mkdir -p /usr/local/java
RUN mkdir -p /usr/local/maven/repository
COPY soft/apache-maven-3.5.4/* /usr/local/
COPY soft/jre1.8.0_212/* /usr/local/java/
2. apply in K8S is success.
root >> ls -al /opt/dockerfile/jenkins/01
root >> kubectl apply -f /opt/dockerfile/jenkins/01
root >> kubectl get all -n kube-ops -o wide | grep jenkins
3. Open in jenkins website, but install jenkins feature happen issue. - Whether I choose recommendation or customization, the same error is prompted during feature installation.
input the dockerfile created init password as below:
finnally, the jenkins website return same error as below：No such plugin: cloudbees-folder
Attachments
Activity
Hi colleague,
As I manual add plugin file 'cloudbees-folder.hpi' in jenkins install path, there alse can't install jenkins plugin correct as below:
upload cloudbees-folder.hpi in jenkins path
retry install jenkins plugin, also happen error
Hi all,
this problem is also caused by conatainer 's /etc/resolv.conf error.
fix solution as below:
1. 修改VM机器上的resolv.conf文件，增加namesever = K8S_DNS_IP
[root@CNT7XDCK11D01 ~]# cat /etc/resolv.conf
; generated by /usr/sbin/dhclient-script
search default.svc.cluster.local svc.cluster.local cluster.local
nameserver 192.168.3.1
nameserver 10.3.0.2
[root@CNT7XDCK11D01 ~]#
2. 修改VM机器上的网卡ifcfg-eno01文件
增加DNS2=K8S_DNS_IP
[root@CNT7XDCK11D02 ~]# vi /etc/sysconfig/network-scripts/ifcfg-eno01
DEVICE="eno01"
NAME="eno01"
BOOTPROTO="static"
BROADCAST="192.168.3.225"
DNS1="192.168.3.1"
DNS2="10.3.0.2"
GATEWAY="192.168.3.1"
HWADDR="xx:xx:xx:xx:xx:xx"
IPADDR="192.168.3.97"
IPV6INIT="yes"
IPV6_AUTOCONF="yes"
NETMASK="255.255.255.0"
NM_CONTROLLED="yes"
ONBOOT="yes"
TYPE="Ethernet"
UUID="xxxxxxxx-xxxx-xxxxx-xxxxx-xxxxxxxxxxxxxxxxxx"
3. the success result as below:
first delete old jenkins resouce from k8s.
root >> kubectl delete service/jenkins-master deployment.apps/jenkins-master -n kube-ops
then re-create the new jenkins resource in k8s,
root >> kubectl apply -f /opt/dockerfile/jenkins/01