Welcome to the Linux Foundation Forum!

Ch 6 Lab 4 pull access denied for jenkins-blueocean repository does not exist or may require docker

Hello,

I'm working through lab4 of LFS261. I'm trying to run docker compose up -d but I'm getting the following warning: ! jenkins Warning pull access denied for jenkins-blueocean, repository does not exist or may require 'docker... 1.1s . I'm also getting this: failed to solve: process "/bin/sh -c jenkins-plugin-cli --plugins blueocean" did not complete successfully: exit code: 1
I'm also getting this warning: WARN[0000] /home/zak/git/devops-repo/setup/docker-compose.yaml: the attributeversionis obsolete, it will be ignored, please remove it to avoid potential confusion

How can I resolve this issue so I can setup the lab?

Thanks.

Welcome!

It looks like you're new here. Sign in or register to get started.
Sign In

Comments

  • Hi @zacts,

    1.- I was unable to reproduce the error. I just got the same warning message, but it continued to the end, then I was able to run and access it.

    2.- What OS and version are you using? Are you running a VM, a cloud system?

    3.- What git version are you using?

    Regards,
    Luis.

  • Posts: 42

    Hello,

    I'm still getting an error to where I can't access a running Jenkins instance: failed to solve: process "/bin/sh -c jenkins-plugin-cli --plugins blueocean" did not complete successfully: exit code: 1. A running Jenkins instance does not show up when I run docker ps or docker ps -a.

    bash-$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 24.04.1 LTS Release: 24.04 Codename: noble

    I'm running this directly on my laptop which is running Ubuntu 24.04 LTS. bash-$ git version gives git version 2.43.0
    . docker version gives `bash-$ docker version
    Client: Docker Engine - Community
    Version: 27.3.1
    API version: 1.47
    Go version: go1.22.7
    Git commit: ce12230
    Built: Fri Sep 20 11:40:59 2024
    OS/Arch: linux/amd64
    Context: default

    Server: Docker Engine - Community
    Engine:
    Version: 27.3.1
    API version: 1.47 (minimum version 1.24)
    Go version: go1.22.7
    Git commit: 41ca978
    Built: Fri Sep 20 11:40:59 2024
    OS/Arch: linux/amd64
    Experimental: false
    containerd:
    Version: 1.7.22
    GitCommit: 7f7fdf5fed64eb6a7caf99b3e12efcf9d60e311c
    runc:
    Version: 1.1.14
    GitCommit: v1.1.14-0-g2c9f560
    docker-init:
    Version: 0.19.0
    GitCommit: de40ad0
    `

  • Posts: 42

    I did look into this a bit on my own, and if I edit the Dockerfile and yaml file to not rely on blueocean and to use the latest jenkins:slim it seem to work for me. I do want to stick as close as possible to the actual course versions for everything though.

  • Hi @zacts,

    I didn't experience the error you got. But if you can run any jenkins container without the 'blueocean' plugin, it will be okey, as you can install it later:

    https://www.jenkins.io/doc/book/blueocean/getting-started/

    So, at least for this lab you are good to go with the workaround you found.

    Regards,
    Luis.

  • Posts: 42

    Thanks

  • It's a pleasure :)

    Luis.

Welcome!

It looks like you're new here. Sign in or register to get started.
Sign In

Welcome!

It looks like you're new here. Sign in or register to get started.
Sign In

Categories

Upcoming Training