linux – 与Jenkins Docker插件和Jenkins Docker Slaves混淆

因此,我在某些方面感到惊喜,看到Jenkins Docker插件将Docker镜像“推送”到我的Docker主机金属,但它也让人感到困惑,因为我的构建发生在Docker Slave Containers中,它运行在Docker主机金属上.甚至我的Jenkins大师都在Docker容器中运行,而不是直接在金属上运行……

在这个流行的Jenkins master/slave guide之后,我到达了Jenkins构建于ephemeral Docker containers的工作点.

这意味着,当我为Jenkins构建一些源代码软件组件/服务时,构建工作将在Jenkins slave中启动,它恰好是Jenkins Docker Plugin创建的Docker Container.

Jenkins工作空间位于此从属容器中,安装了Docker Plugin的Jenkins主机将在构建完成后处理此从属容器.查看我帮助解释的图表：

消化此图后,一些重要的跟进点：

> Jenkins Master和Jenkins Slave此时正在运行相同的Docker Host Metal,因为我刚刚开始运行这个系统
>我正在使用Docker Plugin和SSH Slaves插件来完成此设置

因此,在这个Docker Slave中创建了我的软件组件/服务构建工件,例如,它可以是.dll或.war.碰巧是我的构建工件将是Docker镜像.为了清楚起见,我正在一个正在运行的Docker容器(Jenkins Slave)中构建一个Docker镜像.

我的困惑始于我的期望,我应该明确地运行cmd将我的软件组件Docker镜像构建工件推送到Docker注册表.否则,当Jenkins构建作业完成后,Docker插件将关闭Docker容器slave,处理(rm)从属容器,而且我将丢失该slave容器内的构建工件.

实际发生的事情,以及为什么我惊喜,至少在短期内,当我开始运行devops时,构建工件Docker图像显示在Docker主机金属,docker image ls上.

我很惊讶Docker插件会达到这个级别的假设/帮助…我知道Docker插件允许你配置一个Docker注册表,你可以添加一个构建步骤来构建/发布到Docker Cloud我假设该云被视为图像的注册表,也可能是运行这些图像的地方：

特别有趣的是我没有使用Docker插件进行任何构建步骤,我只是使用Docker插件为构建Jenkins项配置一个Slave容器：

我唯一的构建步骤是执行Shell脚本,是的,这个脚本最终构建了一个Docker镜像,但Docker插件不会知道这个：

Docker插件旋转了Docker Slave Containers,我配置了Docker插件并告诉它一个Docker主机(在我的情况下我的金属)一个Cloud是Docker插件调用Docker主机以及Docker从属映像在Docker主机上使用/云：

我是否只是误解了Jenkins在Docker从属容器内部构建工作空间时的孤立程度？

Docker插件是否只是默认使用了唯一的Docker Cloud(我的Docker主机金属)我为所有任何docker命令设置了我碰巧在Jenkins Docker从属容器内运行？ (通过安装Docker-CE的方式的从属容器)

我的jenkins大师Dockerfile：

#reference
#https://engineering.riotgames.com/news/putting-jenkins-docker-container

FROM jenkins:2.60.1
MAINTAINER Brian Ogden

USER root

#Timezone
ENV TZ=America/Los_Angeles
RUN ln -snf /usr/share/zoneinfo/$TZ /etc/localtime && echo $TZ > /etc/timezone

# Prep Jenkins Directories
RUN mkdir /var/log/jenkins
RUN mkdir /var/cache/jenkins
RUN chown -R jenkins:jenkins /var/log/jenkins
RUN chown -R jenkins:jenkins /var/cache/jenkins

# Copy in local config filesfiles
COPY plugins.sh /usr/local/bin/plugins.sh
RUN chmod +x /usr/local/bin/plugins.sh

# Install default plugins
# Set list of plugins to download / update in plugins.txt like this
# pluginID:version
# credentials:1.18
# maven-plugin:2.7.1
# ...
# NOTE : Just set pluginID to download latest version of plugin.
# NOTE : All plugins need to be listed as there is no transitive dependency resolution.
COPY plugins.txt /tmp/plugins.txt
RUN /usr/local/bin/plugins.sh /tmp/plugins.txt

USER jenkins

#give Jenkins a nice 8 GB memory pool and room to handle garbage collection
#ENV JAVA_OPTS="-Xmx8192m"
#give Jenkins a nice base pool of handlers and a cap
#ENV JENKINS_OPTS="--handlerCountStartup=100 --handlerCountMax=300"

ENV JENKINS_OPTS="--logfile=/var/log/jenkins/jenkins.log --webroot=/var/cache/jenkins/war"

我使用docker-compose和Docker卷与我的Jenkins Master,我的docker-compose.yml：

version: '2'
services:
  data:
    build: data
    image: tsl.devops.jenkins.data.image
    container_name: tsl.devops.jenkins.data.container
  master:
    build: master
    image: tsl.devops.jenkins.master.image
    container_name: tsl.devops.jenkins.master.container
    volumes_from:
      - data
    ports:
      - "50000:50000"
    #network_mode: "host"
  nginx:
    build: nginx
    image: tsl.devops.jenkins.nginx.image
    container_name: tsl.devops.jenkins.nginx.container
    ports:
      - "80:80"
    links:
      - master:jenkins-master
  slavebasic:
    build:
      context: ./slaves
      dockerfile: basic/Dockerfile
    image: tsl.devops.jenkins.slave.basic.image
    container_name: tsl.devops.jenkins.slave.basic.container
  slavedotnetcore:
    build:
      context: ./slaves
      dockerfile: dotnetcore/Dockerfile
    image: tsl.devops.jenkins.slave.dotnetcore.image
    container_name: tsl.devops.jenkins.slave.dotnetcore.container

我的Jenkins Master卷/驱动器Dockerfile：

#reference
#https://engineering.riotgames.com/news/docker-jenkins-data-persists
FROM centos:7
MAINTAINER Brian Ogden

#create the Jenkins user in this container
RUN useradd -d "/var/jenkins_home" -u 1000 -m -s /bin/bash jenkins
#NOTE: we set the UID here to the same one the Cloudbees Jenkins image uses 
#so we can match UIDs across containers,which is essential if you want 
#to preserve file permissions between the containers. We also use the same home directory and bash settings.

#Jenkins log directory
RUN mkdir -p /var/log/jenkins
RUN chown -R jenkins:jenkins /var/log/jenkins

#Docker volume magic
VOLUME ["/var/log/jenkins","/var/jenkins_home"]
USER jenkins

#just a little output reminder of the container's purpose
CMD ["echo","Data container for Jenkins"]

我的奴隶Dockerfile：

FROM centos:7
MAINTAINER Brian Ogden

#the USER will be root by default just explicitly 
#expressing it for better documentation
USER root

# Install Essentials
RUN yum update -y && \
         yum clean all

#############################################
# Jenkins Slave setup
#############################################
RUN yum install -y \
    git \
    wget \
    openssh-server \
    java-1.8.0-openjdk \
    sudo \
    make && \
    yum clean all

# gen dummy keys,centos doesn't autogen them like ubuntu does
RUN /usr/bin/ssh-keygen -A

# Set SSH Configuration to allow remote logins without /proc write access
RUN sed -ri 's/^session\s+required\s+pam_loginuid.so$/session optional pam_loginuid.so/' /etc/pam.d/sshd

# Create Jenkins User
RUN useradd jenkins -m -s /bin/bash

# Add public key for Jenkins login
RUN mkdir /home/jenkins/.ssh
COPY /files/id_rsa.pub /home/jenkins/.ssh/authorized_keys

#setup permissions for the new folders and files
RUN chown -R jenkins /home/jenkins
RUN chgrp -R jenkins /home/jenkins
RUN chmod 600 /home/jenkins/.ssh/authorized_keys
RUN chmod 700 /home/jenkins/.ssh

# Add the jenkins user to sudoers
RUN echo "jenkins  ALL=(ALL)  ALL" >> etc/sudoers
#############################################

#############################################
# Docker and Docker Compose Install
#############################################
#install required packages
RUN yum install -y \
    yum-utils \
    device-mapper-persistent-data \
    lvm2 \
    curl && \
    yum clean all

#add Docker CE stable repository
RUN yum-config-manager \
    --add-repo \
    https://download.docker.com/linux/centos/docker-ce.repo

#Update the yum package index.
RUN yum makecache fast

#install Docker CE
RUN yum install -y docker-ce-17.06.0.ce-1.el7.centos

#install Docker Compose 1.14.0
#download Docker Compose binary from github repo
RUN curl -L https://github.com/docker/compose/releases/download/1.14.0/docker-compose-`uname -s`-`uname -m` > /usr/local/bin/docker-compose
#Apply executable permissions to the binary
RUN chmod +x /usr/local/bin/docker-compose
#############################################

#############################################
# .NET Core SDK
#############################################
RUN yum install -y \
    libunwind \
    libicu

RUN curl -sSL -o dotnet.tar.gz https://go.microsoft.com/fwlink/?linkid=848821
RUN mkdir -p /opt/dotnet && tar zxf dotnet.tar.gz -C /opt/dotnet
RUN ln -s /opt/dotnet/dotnet /usr/local/bin

#add Trade Service Nuget Server
RUN mkdir -p /home/jenkins/.nuget/NuGet
COPY /files/NuGet.Config /home/jenkins/.nuget/NuGet/NuGet.Config

RUN chown -R jenkins /home/jenkins/.nuget
RUN chgrp -R jenkins /home/jenkins/.nuget

RUN chmod 600 /home/jenkins/.nuget/NuGet/NuGet.Config
RUN chmod 700 /home/jenkins/.nuget/NuGet

#speed up dotnet core builds
ENV NUGET_XMLDOC_MODE skip
ENV DOTNET_SKIP_FIRST_TIME_EXPERIENCE true
#############################################

# Expose SSH port and run SSHD
EXPOSE 22
#Technically,the Docker Plugin enforces this call when it starts containers by overriding the entry command. 
#I place this here because I want this build slave to run locally as it would if it was started in the build farm.
CMD ["/usr/sbin/sshd","-D"]

一个示例软件/组件Dockerfile,它将在Jenkins Slave Docker容器中创建一个Docker镜像构建工件：

FROM centos:7
MAINTAINER Brian Ogden

#Timezone
ENV TZ=America/Los_Angeles
RUN ln -snf /usr/share/zoneinfo/$TZ /etc/localtime && echo $TZ > /etc/timezone

RUN yum update -y && \
         yum clean all

#############################################
# .NET Core SDK
#############################################
RUN yum install -y \
    libunwind \
    libicu

RUN curl -sSL -o dotnet.tar.gz https://go.microsoft.com/fwlink/?linkid=848821
RUN mkdir -p /opt/dotnet && tar zxf dotnet.tar.gz -C /opt/dotnet
RUN ln -s /opt/dotnet/dotnet /usr/local/bin

#speed up dotnet core builds
ENV NUGET_XMLDOC_MODE skip
ENV DOTNET_SKIP_FIRST_TIME_EXPERIENCE true
#############################################

#############################################
# .NET Sevrice setup
#############################################
ARG ASPNETCORE_ENVIRONMENT

# Copy our code from the "/src/MyWebApi/bin/Debug/netcoreapp1.1/publish" folder to the "/app" folder in our container
WORKDIR /app
COPY ./src/TSL.Security.Service/bin/Debug/netcoreapp1.1/publish .

# Expose port 5000 for the Web API traffic
ENV ASPNETCORE_URLS http://+:5000
ENV ASPNETCORE_ENVIRONMENT $ASPNETCORE_ENVIRONMENT 

EXPOSE 5000

# Run the dotnet application against a DLL from within the container
# Don't forget to publish your application or this won't work
ENTRYPOINT ["dotnet","TSL.Security.Service.dll"]
#############################################

解决方法

根据您的Docker插件配置,您使用172.17.0.1作为Docker主机.从slave或master容器,这将是在主机上运行的Docker守护程序(Docker中没有Docker发生在这里).当您的Jenkins从站构建映像时(无论从站是作为容器运行还是在主机上运行),它正在使用主机上的Docker,这就是您的映像显示在主机上的原因.

值得注意的是,数据可能首先进入奴隶使用的Docker卷(根据Jenkins Dockefile在https://github.com/jenkinsci/docker/blob/9f29488b77c2005bbbc5c936d47e697689f8ef6e/Dockerfile,默认为/ var / jenkins_home).在您的情况下,这只是来自数据服务的卷(但是,在Compose v2格式中,您只需定义命名卷,您不需要创建数据容器).从这里开始,您的代码和Dockerfile将通过tcp：//172.17.0.1:4243上的API发送到主机上的Docker构建上下文.

linux – 与Jenkins Docker插件和Jenkins Docker Slaves混淆

解决方法

相关推荐