dd010101
commented
1 month ago Yeah, seems like overreaction is their motto.
let's focus focus only on equuleus. Skip sagitta references for now.
Jenkins doesn't have access to your local registry. This is related to part: Build patched vyos-build docker image and create local registry https://github.com/dd010101/vyos-jenkins#build-patched-vyos-build-docker-image-and-create-local-registry and Declarative Pipeline (Docker) https://github.com/dd010101/vyos-jenkins?tab=readme-ov-file#configure-dev_packages_vyos_net_host-variable-and-add-global-vyos-build-jenkins-library
You need start local registry, otherwise jenkins will just use dockerhub that's the docker run -d -p 5000:5000 --restart always --name registry registry:2.7 command, and this is where you have problem, you specified Declarative Pipeline (Docker) and that's seems ok but jenkins can't connect for some reason to the registry, is the local registry running? docker ps -a? Do you have port 5000 on 10.1.1.94 open?
The port 5000 acts like webserver and returns brackets if you probe curl 10.1.1.94:5000/v2/ && echo:
root@vyos-jenkins:~# curl 172.17.17.17:5000/v2/ && echo
{}Make sure registry is listening where it should.
Private docker hub isn't needed, I did succeed just by using the local registry alone.
EDIT: I did verify how this works and it should work as said, there is one additional step but that comes after so you didn't get there yet, with the original instructions you may end-up with error Error response from daemon: manifest for 172.17.17.17:5000/vyos/vyos-build:equuleus not found: manifest unknown: manifest unknown because I omitted the part where you push the created images to the local registry, see readme for details https://github.com/dd010101/vyos-jenkins?tab=readme-ov-file#build-patched-vyos-build-docker-image-and-create-local-registry
aldemaroc
ibehren1
@dd010101
So nice that they cut us off on the forum... Appreciate the work you have been doing in documenting.
I was going through testing this evening and got to the point of building the first package (dropbear). It is failing to pull the custom container images from the local registry.
Is there a step missing for setting up docker to listen on network port. I may just try pushing to my private repo on Docker Hub tomorrow.
Suggestions?
isaac @ behrenshome . com