This is intentional because the Blue Ocean container has Docker CLI commands added which makes the rest of the tutorial work properly.

Basically, this was an intentional decision

R. Tyler Croy In such case the page should have a notice about the official jenkins/jenkins image at least.
Otherwise it confuses Jenkins users.

Will modify the page

CC Baptiste Mathus who was also concerned about this issue. And also Mark Waite

With the discussion about the BO future in https://groups.google.com/forum/#!topic/jenkinsci-dev/zNukeuLK4Og , this issue becomes even a bigger concern IMO

I've read the installation tutorial page at https://jenkins.io/doc/book/installing/#downloading-and-running-jenkins-in-docker. I don't find anything in that tutorial which persuades me that it needs to use the blue ocean image instead of the standard image.

However, the other tutorials (like the maven, node, and python tutorials) all require a docker step in Pipeline. I think that's what R. Tyler Croy meant when he said:

the Blue Ocean container has Docker CLI commands added which makes the rest of the tutorial work properly.

Mark Waite second sentence in the tutorial is "The recommended Docker image to use is the jenkinsci/blueocean image (from the Docker Hub repository).". Looks like persuasion imho

I agree it is persuasion. I'm fine if we want to change the "Installing" page to recommend the jenkins/jenkins docker image. The three tutorials already give instructions to use the blueocean image for the tutorials.

We likely also need to provide additional instructions for other types of installations (helm chart, etc.). I assume that's a future task while changing the recommended default is a more immediate task.

It is fine to have both images in guidelines, but then we should start from jenkins/jenkins and then provide some pros/cons comparison

Having a dedicated image for Blue Ocean does not make sense for users. Might be useful for demos, but that is it. We should guide users to either

• Run jenkins/jenkins as is and use the Setup Wizard to install recommend plugins.
• Produce a derivative image with declarative plugin configuration somehow aligned with S.W. recommendations.
• Run Evergreen.

I would be in favor of a good BlueOcean image as a helpful bundle, but there is a serious UX issue in the current image: JENKINS-52069. jenkinci/blueocean is that plugins.txt is NOT compatible with the installation wizard. So it causes a really messy UX for thos who does not use Configuration-as-code. And there is no much sense to use the image with Configuration-as-code, because it can be easily defined in plugins.txt: https://github.com/oleg-nenashev/jenkins-blueocean-experimental/blob/java11/plugins.txt

So I am in favor of deprecating the image if there is no plan to invest into improving it. And there is a dev list thread which suggests that there is no immediate plans for that: https://groups.google.com/forum/#!msg/jenkinsci-dev/zNukeuLK4Og/KP3mfQ2ZFAAJ

I filled https://github.com/jenkins-infra/jenkins.io/pull/2148 to track this.

Adrien Lecharpentier given the comments in the PR I assume this needs changes before it can be reviewed again (hence the status change in review->in progress).

Would be great to get it over the line

New issue in GitHub: https://github.com/jenkins-infra/jenkins.io/issues/3315

New GitHub PRs https://github.com/jenkins-infra/jenkins.io/pull/3843 and https://github.com/jenkins-infra/jenkins.io/pull/3852 attempt to resolve this.

Currently Jenkins Docker installation guidelines recommend recommend official Jenkins Docker image.  See https://jenkins.io/doc/book/installing/#downloading-and-running-jenkins-in-docker . This is achieved by successfully merging a set of PRs, including the following ones:
https://github.com/jenkins-infra/jenkins.io/pull/3543

https://github.com/jenkins-infra/jenkins.io/pull/3843

https://github.com/jenkins-infra/jenkins.io/pull/3852

https://github.com/jenkins-infra/jenkins.io/pull/3874

https://github.com/jenkins-infra/jenkins.io/pull/3919

Now the same approach of using Official jenkins/jenkins docker image, is utilized by both link Running Jenkins in Docker in Installing Jenkins and by link Using build tools in Jenkins Tutorials

Jenkins Docker image install instructions use Java 11 and provide the Blue Ocean plugins. I believe this is resolved