Lab 4 error in "docker-compose build" - versions compatibility

ashraf.fouad

Hello

I'm in the course chapter 6: SETTING UP CONTINUOUS INTEGRATION WITH JENKINS
In the video: Launching Jenkins with Docker

I'm running the command:
docker-compose build

I'm getting the following error:

 => [7/8] RUN curl -L "https://github.com/docker/compose/releases/download/1.27.4/docker-compose-$(uname -s)-$(uname -m)" -o /usr/local/bin/docker-co  3.3s
 => ERROR [8/8] RUN jenkins-plugin-cli --plugins blueocean:1.24.3                                                                                     10.9s
------


  [8/8] RUN jenkins-plugin-cli --plugins blueocean:1.24.3:


#11 10.83
#11 10.83 github-branch-source (2.10.2) requires a greater version of Jenkins (2.271) than 2.263.1 in /usr/share/jenkins/jenkins.war
------
executor failed running [/bin/sh -c jenkins-plugin-cli --plugins blueocean:1.24.3]: exit code: 1
ERROR: Service 'jenkins' failed to build : Build failed

My environment:
Windows 10 (10.0.19044)
Docker client:
Version: 20.10.14
Server: Docker Desktop 4.7.1 (77678)
Version: 20.10.14

ashraf.fouad

To try fixing it, I have changed the Dockerfile to include
FROM jenkins/jenkins:2.277.4-lts-slim
Just selected LTS version higher than the error I'm receiving, and the build worked file.

But when I issue the command docker image ls I get one image only which is

$ docker image ls
REPOSITORY          TAG       IMAGE ID       CREATED          SIZE
jenkins-blueocean   latest    733507f8739d   22 minutes ago   812MB

The video is mentioning I should be seeing 2 images, the other one is for jenkins/jenkins

I proceeded with the video, and setup jenkins, and it worked and I can access jenkins dashboard.

The total number of images now after running the command docker-compose up -d is two including the following:

$ docker image ls
REPOSITORY          TAG       IMAGE ID       CREATED          SIZE
jenkins-blueocean   latest    733507f8739d   11 minutes ago   812MB
docker              dind      9e4abd47de51   3 days ago       311MB

luisviveropena

Hi @ashraf.fouad ,

The git repo has been updated just a couple of days ago and it's working now. So you can clean the browser's cache, get the code again and try it.

Regards,
Luis.

gouravshah

Thats right. The image now is been updated to jenkins/jenkins:2.347-slim

otoolb

This seems to be broken again. Here is the full error:

 => ERROR [jenkins 8/8] RUN jenkins-plugin-cli --plugins blueocean                                                                                                            3.5s
------                                                                                                                                                                             


  [jenkins 8/8] RUN jenkins-plugin-cli --plugins blueocean:


2.043 Dec 12, 2023 10:40:14 PM org.apache.http.impl.execchain.RetryExec execute                                                                                                    
2.043 INFO: I/O exception (org.apache.http.NoHttpResponseException) caught when processing request to {s}->https://updates.jenkins.io:443: The target server failed to respond     
2.043 Dec 12, 2023 10:40:14 PM org.apache.http.impl.execchain.RetryExec execute
2.043 INFO: Retrying request to {s}->https://updates.jenkins.io:443
3.491 Plugin prerequisite not met:
3.491 
3.491 cloudbees-folder (6.815.v0dd5a_cb_40e0e) requires a greater version of Jenkins (2.375.1) than 2.375
------
failed to solve: process "/bin/sh -c jenkins-plugin-cli --plugins blueocean" did not complete successfully: exit code: 1

otoolb

My solution has been to update the FROM line to use the bugfixed version of jenkins (keeping the same minor version)

FROM jenkins/jenkins:2.375.4-jdk11

This should be an appropriate solution with minimal disruption to the lab. So far the container builds. I will update more if I run into any other issues later in the lab because of this change.

ericegan

Thank you @otoolb! I will look into updating this.

fsierra

@otoolb said:
My solution has been to update the FROM line to use the bugfixed version of jenkins (keeping the same minor version)

FROM jenkins/jenkins:2.375.4-jdk11

This should be an appropriate solution with minimal disruption to the lab. So far the container builds. I will update more if I run into any other issues later in the lab because of this change.

btw had to update to 2.401.3 due to multiple errors/unsatisfied version dependecies. (mentioned 2.387.3 was not enough to remove all dependecy errors)
e.g.

Step 10/10 : RUN jenkins-plugin-cli --plugins blueocean
 ---> Running in b6416fd83fa9
Multiple plugin prerequisites not met:

mina-sshd-api-core (2.12.1-101.v85b_e08b_780dd) requires a greater version of Jenkins (2.387.3) than 2.375.4,

github-branch-source (1771.v59b_6a_fa_1b_89e) requires a greater version of Jenkins (2.387.3) than 2.375.4,

commons-text-api (1.11.0-94.v3e1f4a_926e49) requires a greater version of Jenkins (2.387.3) than 2.375.4,

....

Isn't it ironic when SRE course fails to set up an automation/CI, which would run the Dockerfile/docker-compose.yaml once a week to test and report if the container image still builds or fails and the course content needs to be updated?

luisviveropena

Hi @fsierra,

Thanks for informing us of this. I was able to reproduce the issue. It also gets fixed with jenkins/jenkins:latest (at this day and time at least).

Regards,
Luis.