Hi @fasolens, you probably want the normal https://gitter.im/jenkinsci/jenkins channel is more geared towards using the docker containers that Jenkins provides
Hello All, good afternoon to you. I'm looking for a little help to better understand the docker jenkins/inbound-agent image. I've lots of jobs that need tools installing on the inbound-agent. I'd like to check my understanding is correct and that if i wish to install build tools on to the agent I'll need to make my own docker file and then install via apt-get or yum. Sorry I'm not actually clear what o/s the agent is running.
Second part of the question... If i try and start the jenkins/inbound-agent locally on my laptop, with a view to then login via docker exec interactive bash shell etc etc. I can't because the image won't actually start unless it can connect to a jenkins master. Is there any way around this to allow me to test my build tools?
Second part of the question... If i try and start the jenkins/inbound-agent locally on my laptop, with a view to then login via docker exec interactive bash shell etc etc. I can't because the image won't actually start unless it can connect to a jenkins master. Is there any way around this to allow me to test my build tools?
Thanks for replying Alex, currently if i use docker run --init jenkins/inbound-agent
without the docker run --init jenkins/inbound-agent -url http://jenkins-server:port <secret> <agent name> set it just moans that it expects these values to be set.
if I set them to fake details because I don't have a local master etc, so something like
docker run --init jenkins/inbound-agent -url http://jenkins-server:80 mypass mylocalagent
the docker images fires up fails to connect to the master and terminates.
without the docker run --init jenkins/inbound-agent -url http://jenkins-server:port <secret> <agent name> set it just moans that it expects these values to be set.
if I set them to fake details because I don't have a local master etc, so something like
docker run --init jenkins/inbound-agent -url http://jenkins-server:80 mypass mylocalagent
the docker images fires up fails to connect to the master and terminates.
any way to start it and not try and connect, fail and then terminate
something like that ^^
Thought that was the standard jenkins image.
There is a
slimvariant that uses Debian slim and an Alpine variant for those who prefer Alpine
Including uucp?
The goal of the Docker image is to provide a working environment for many uses cases, not to provide the minimum distribution that will allow Jenkins to start. Jenkins will start without installing command line git and without installing git-lfs, but users have preferred a working environment over a minimal environment. The
alpine tag is more likely what you want if you're seeking a minimal environment
At that point you can layer whatever distro you like.
Layering the distro on top of jenkins solves them with a single jenkins distro: slap anything you like on it: Arch, Gentoo, Debian, RH... or a subset that doesn't include pieces with security issues that prevent using it in the first place because the distros include problematic executables.
Yes. Plugins can be installed locally in a custom Docker image. Refer to https://github.com/jenkinsci/docker#preinstalling-plugins for a way to define a
plugins.txt file that will allow you to build a Docker image where you have network access, then you can transport the created image into the environment that has no network access.
Sanity check: JENKINS_UC='https://localhost' would leave everything coming from the local system?
You probably want to read https://www.jenkins.io/doc/book/installing/#offline-jenkins-installation if you're considering an offline installation of Jenkins. That's a recent arrival in the documentation thanks to the efforts of the UX Hackfest in late May. If you find mistakes or flaws in that document, pull requests would be much appreciated to update or correct its content
Is there a tool or plugin to silently build and instantiate a docker image with Jenkins inside? I would expect it to have functionality similar e.g. to maven archetype plugin, allowing to create from cli a wide range of Jenkins apps. This range may be from a quickstart “hello world” to multi cluster k8s deployments and beyond. IMO simplicity of usage for such tool may attract many new Jenkins adopters.
2 replies
@vsilverman there is
custom war packager that will create a custom war file that includes a set of plugins and other configurations. There is the Google Summer of Code project "Custom Jenkins distribution build service" currently running that is creating something that might be similar to what you're envisioning.
Thanks @MarkEWaite for sharing CWP plugin. I had looked at https://www.jenkins.io/blog/2018/10/16/custom-war-packager/ - it may be a good base point to start further development