Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to build docker image or clone in Windows #88

Open
jsgrover2k25 opened this issue Jan 30, 2025 · 4 comments
Open

Unable to build docker image or clone in Windows #88

jsgrover2k25 opened this issue Jan 30, 2025 · 4 comments

Comments

@jsgrover2k25
Copy link

jsgrover2k25 commented Jan 30, 2025

Using Windows 11 Version 10.0.22631 Build 22631
Using Docker version 27.4.0, build bde2b89

Build Error

Image

Cloning Error

Image

I got it to work by changing the windows image version number, but I don't know how to fix the build

docker run --name jenkins-blueocean --restart=on-failure --detach --network jenkins --env DOCKER_HOST=tcp://docker:2376 --env DOCKER_CERT_PATH=/certs/client --env DOCKER_TLS_VERIFY=1 --volume jenkins-data:/var/jenkins_home --volume jenkins-docker-certs:/certs/client:ro --publish 8080:8080 --publish 50000:50000 myjenkins-blueocean:2.332.3-1

@jsgrover2k25
Copy link
Author

Figured out my build issue for this command: docker build -t myjenkins-blueocean:2.414.2 .

I was using a filter DNS server in my firewall, to block unsafe sites, I had to change from such a restrictive DNS server to a more open DNS server.

@QATester35D
Copy link

QATester35D commented Feb 3, 2025

@jsgrover2k25 I'm getting the same build error (the clone seemed to be fine). Can you share the firewall setting you changed that was restricting it? Thanks.

Image

Image

@jsgrover2k25
Copy link
Author

I am using DNS server from clearbrowsing.org

I was block using these DNS addresses of IPv4:
185.229.168.10
185.229.169.11

However, I was free to build with
185.229.168.9
185.229.169.9

@QATester35D
Copy link

QATester35D commented Feb 4, 2025

@jsgrover2k25 thanks for your response. I was able to get around my problem before your reply by simplifying the dockerfile reference to letting the build process pull down the latest versions worked. I changed the dockerfile to use “lts-jdk17” which installs the latest stable release, and I dropped off the versions related to blueocean and docker-workflow. By doing this it will grab the latest versions and it appeared (at least in PowerShell) that I got a clean install.

However in Jenkins I get errors in the "Manage Jenkins" section.
Some plugins could not be loaded due to unsatisfied dependencies. Fix these issues and restart Jenkins to re-enable these plugins. It appears there is an issue with the Token Macro Plugin. Due to this it seems to have a ripple effect on the Blue Ocean plugin. So now I'm trying to resolve this Token Macro Plugin issue.

    Dependency errors:
    
    Token Macro Plugin (442.v4f452dc3c7c0)
    Plugin is missing: json-path-api (2.9.0-118.v7f23ed82a_8b_8)
    Some of the above failures also result in additional indirectly dependent plugins not being able to load.
    
    Indirectly dependent plugins:
    
    GitHub Pipeline for Blue Ocean (1.27.16)
    Failed to load: Pipeline implementation for Blue Ocean (blueocean-pipeline-api-impl 1.27.16)
    ...<followed by lots of Blue Ocean failures>

Scratch the last part...in Jenkins within Manage Jenkins where the errors were showing, I clicked the Correct button and like before it brought me to another plugins page that was empty. However this time when I clicked the refresh button I got an update. I ran the update and then the part I really think made a difference (forgot to do this yesterday) was to stop and start the container since I'm running this through Docker. Now when I just logged back in the Manage Jenkins section is clean.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants