@ScottAShipp_twitter you can define Jenkins configuration with the Docker image in several different ways.
For example, files in the
ref directory of the image you define (based on the jenkins/jenkins) will be placed into the working Jenkins image. I used that technique to store job configuration XML files, credential files, and more. Works great. I install plugins that way using a git large file storage repository. Records the exact versions of plugins I'm using without requiring that I insert their version numbers into a configuration file.
You can define the exact version of plugins you want and call the plugin install script as described at https://github.com/jenkinsci/docker/blob/master/README.md#preinstalling-plugins .
If you'd like to see a sample, refer to https://github.com/MarkEWaite/docker-lfs/tree/lts-with-plugins
You can use the configuration as code plugin and define your Jenkins configuration with a YAMLfile in the Docker image
docker.image('maxys/docusaurus-pdf:latest').withRun ("from-build --no-sandbox -v /var/jenkins_home/workspace/docs:/workspace -o /workspace/build/internal.pdf /workspace/build docs/Docusaurus/DocusaurusGetStarted docs")in any way?
--and when I do it the way above Jenkins try to pull 'customArgument' image.
docker run -d from-build --no-sandbox -o build/img/internal.pdf build docs/Docusaurus/DocusaurusGetStarted docs maxys/docusaurus-pdf:latest Unable to find image 'from-build:latest' locally docker: Error response from daemon: pull access denied for from-build, repository does not exist or may require 'docker login': denied: requested access to the resource is denied.
slimvariant that uses Debian slim and an Alpine variant for those who prefer Alpine
alpinetag is more likely what you want if you're seeking a minimal environment