使用官方Jenkins镜像进行容器部署
2018-11-02 本文已影响328人
do_young
背景
Jenkins在hub.docker上的最新版本是基于2.60.3版本的jenkins制作的镜像。
当初始化安装插件的时候,很多的插件都无法在上面成功安装,从提示的异常信息来看,应该是jenkins在版本及插件维护上没有考虑向下兼容或者是维护得不好。
在hub.docker上给出了2.60.3版本的jenkins镜像生成的工程,所以我的思路就是不纠结于如何解决插件的兼容性问题。将镜像中的jenkins直接升级到最新版本。
备注:本人是于2018年11月1日生成的镜像,当前最新jenkins版本为:2.149
生成最新镜像
将生成镜像的工程下载到本地主机上(本人是centos),将以sh为后缀的文件权限进行修改。
sudo chmod 777 *.sh
修改Dockerfile,主要是将下载的jenkins的war进行完整性确认的脚本注释或删除,并修改JENKINS_VERSION变量值为2.149,如下所示:
FROM openjdk:8-jdk
RUN apt-get update && apt-get install -y git curl && rm -rf /var/lib/apt/lists/*
ARG user=jenkins
ARG group=jenkins
ARG uid=1000
ARG gid=1000
ARG http_port=8080
ARG agent_port=50000
ENV JENKINS_HOME /var/jenkins_home
ENV JENKINS_SLAVE_AGENT_PORT ${agent_port}
# Jenkins is run with user `jenkins`, uid = 1000
# If you bind mount a volume from the host or a data container,
# ensure you use the same uid
RUN groupadd -g ${gid} ${group} \
&& useradd -d "$JENKINS_HOME" -u ${uid} -g ${gid} -m -s /bin/bash ${user}
# Jenkins home directory is a volume, so configuration and build history
# can be persisted and survive image upgrades
VOLUME /var/jenkins_home
# `/usr/share/jenkins/ref/` contains all reference configuration we want
# to set on a fresh new installation. Use it to bundle additional plugins
# or config file with your custom jenkins Docker image.
RUN mkdir -p /usr/share/jenkins/ref/init.groovy.d
ENV TINI_VERSION 0.14.0
ENV TINI_SHA 6c41ec7d33e857d4779f14d9c74924cab0c7973485d2972419a3b7c7620ff5fd
# Use tini as subreaper in Docker container to adopt zombie processes
RUN curl -fsSL https://github.com/krallin/tini/releases/download/v${TINI_VERSION}/tini-static-amd64 -o /bin/tini && chmod +x /bin/tini \
&& echo "$TINI_SHA /bin/tini" | sha256sum -c -
COPY init.groovy /usr/share/jenkins/ref/init.groovy.d/tcp-slave-agent-port.groovy
# jenkins version being bundled in this docker image
ARG JENKINS_VERSION
ENV JENKINS_VERSION ${JENKINS_VERSION:-2.149}
# jenkins.war checksum, download will be validated using it
ARG JENKINS_SHA=2d71b8f87c8417f9303a73d52901a59678ee6c0eefcf7325efed6035ff39372a
# Can be used to customize where jenkins.war get downloaded from
ARG JENKINS_URL=https://repo.jenkins-ci.org/public/org/jenkins-ci/main/jenkins-war/${JENKINS_VERSION}/jenkins-war-${JENKINS_VERSION}.war
# could use ADD but this one does not check Last-Modified header neither does it allow to control checksum
# see https://github.com/docker/docker/issues/8331
RUN curl -fsSL ${JENKINS_URL} -o /usr/share/jenkins/jenkins.war
ENV JENKINS_UC https://updates.jenkins.io
ENV JENKINS_UC_EXPERIMENTAL=https://updates.jenkins.io/experimental
RUN chown -R ${user} "$JENKINS_HOME" /usr/share/jenkins/ref
# for main web interface:
EXPOSE ${http_port}
# will be used by attached slave agents:
EXPOSE ${agent_port}
ENV COPY_REFERENCE_FILE_LOG $JENKINS_HOME/copy_reference_file.log
USER ${user}
COPY jenkins-support /usr/local/bin/jenkins-support
COPY jenkins.sh /usr/local/bin/jenkins.sh
ENTRYPOINT ["/bin/tini", "--", "/usr/local/bin/jenkins.sh"]
# from a derived Dockerfile, can use `RUN plugins.sh active.txt` to setup /usr/share/jenkins/ref/plugins from a support bundle
COPY plugins.sh /usr/local/bin/plugins.sh
COPY install-plugins.sh /usr/local/bin/install-plugins.sh
部署
本人是基于k8s的部署,如果是docker的话,也可以参照deployment文件,配置docker run的启动参数。
deployment文件如下:
apiVersion: extensions/v1beta1
kind: Deployment
metadata:
name: jenkins-deployment
namespace: default
spec:
replicas: 1
selector:
matchLabels:
tier: jenkins
template:
metadata:
labels:
tier: jenkins
spec:
containers:
- name: jenkins-container
image: jenkins:latest
imagePullPolicy: IfNotPresent
ports:
- containerPort: 8080
- containerPort: 50000
volumeMounts:
- mountPath: /var/jenkins_home
name: jenkins-home
volumes:
- name: jenkins-home
hostPath:
path: /home/dev_ops/jenkins_home
在应用deployment之前,先将挂载到宿主机的jenkins_home目录进行权限修改,再创建jenkins的deployment。
chome 777 /home/dev_ops/jenkins_home
service文件如下:
apiVersion: v1
kind: Service
metadata:
name: jenkins-service
namespace: default
spec:
type: NodePort
ports:
- port: 8080
targetPort: 8080
name: jenkins-port
nodePort: 8080
selector:
tier: jenkins
启动以后,就可以正常安装插件了。
屏幕快照 2018-11-02 上午11.30.40.png