Hi Everyone, hope all is doing well, I have what might be a fairly easy fix, but any help would be much appreciated
So.. here's what my Dockerfile looks like:
`FROM jenkins/jenkins:latest
ENV JAVA_OPTS -Djenkins.install.runSetupWizard=false
ENV CASC_JENKINS_CONFIG /var/jenkins_home/casc.yaml
COPY plugins.txt /usr/share/jenkins/ref/plugins.txt
RUN /usr/local/bin/install-plugins.sh < /usr/share/jenkins/ref/plugins.txt
COPY casc.yaml /var/jenkins_home/casc.yaml
USER root
RUN apt-get update && apt-get install wget \
&& apt-get install -y nodejs && apt-get install -y npm \
# The current stable google-chrome version is 93 and so ill be installing version 93 for chromedriver
&& wget https://dl.google.com/linux/direct/google-chrome-stable_current_amd64.deb \
&& apt-get install -y ./google-chrome-stable_current_amd64.deb \
&& wget https://chromedriver.storage.googleapis.com/93.0.4577.15/chromedriver_linux64.zip \
&& unzip chromedriver_linux64.zip && mv chromedriver /usr/bin/chromedriverUSER jenkins`
Iv basically installed most of what is needed, I have switched back and forth with google-chrome and chromedriver versions always keeping them at supported versions... but that definitely does not seem to be my issue, until this:
Request failed due to unknown error: Chrome failed to start: crashed
(unknown error: DevToolsActivePort file doesn't exist) and linked it to this: https://bugs.chromium.org/p/chromedriver/issues/detail?id=2473 which is a reoccurring issue with Docker, please can someone give me an example of implementing the work around flags to get my Jenkins Jobs to build.. thank you so much in advance
7 replies
4 replies
pipeline {
agent none
stages {
stage('seeiner-device') {
agent {
docker {
image 'maven:3.6.3-openjdk-8-slim'
args '-v $HOME/.m2:/root/.m2'
}
}
environment {
MAVEN_CLI_OPTS = '-s .m2/settings.xml --batch-mode'
}
steps {
git(url: 'http://xxxxx/citest/seeiner-device.git', branch: 'develop', credentialsId: 'fb10cc6f-04d9-40a5-96e8-7fbe6253339d')
sh '''ls
'''
sh 'mvn $MAVEN_CLI_OPTS clean install'
echo 'Building the docker image'
script {
def dockerImage = docker.build "seeiner/seeiner-device:latest"
}
script {
docker.image('seeiner/seeiner-device:latest').withRun("-d --name seeiner-device -p 17011:17011")
}
}
}
}
}
@LLLLimbo wouldn't you be better served calling the docker commands directly to perform the desired operations rather than using plugin to run attempt to run them?
In the Jenkinsfile definition that you list, the seeiner-device stage is running inside the docker image maven:3.6.3-openjdk-8-slim and then you're trying to execute a docker command with the docker.build step. As far as I understand it, the maven:3.6.3-openjdk-8-slim image does not include the docker command inside that image. A Docker image generally is not used to build another Docker image, at least not as far as I understand it.
1 reply
docker. That agent is a machine where the agent process allowed to run docker commands. It is not a Docker process that is then trying to run another Docker process inside the Docker process
Expected regular expression 'junit.jpi' to match <empty>, but it did not match.