Hi Mark, Thank you for your response. Though, I've gone through the kotacoda tutorial. Would definitely peruse the other links and revert and hope to propose a tutorial that addresses this concern.
Regards. On Tue, Feb 4, 2020, 8:05 PM Mark Waite <mark.earl.wa...@gmail.com> wrote: > You're correct that there is no tutorial on jenkins.io that uses Docker > in Docker to create and publish Docker images. You might consider the > following links as a source of ideas and alternatives (without assuming > that any of the tutorials or articles are endorsed or official or best): > > - Katacoda tutorial on building Docker images with Jenkins > <https://www.katacoda.com/courses/jenkins/build-docker-images> > (listed by Katacoda as an advanced tutorial) > - Why is docker in docker considered bad > > <https://devops.stackexchange.com/questions/676/why-is-docker-in-docker-considered-bad> > ? > - Using Docker in Docker for CI? Think twice > <https://jpetazzo.github.io/2015/09/03/do-not-use-docker-in-docker-for-ci/> > - Jenkins Docker outside of Docker > <https://hub.docker.com/r/psharkey/jenkins-dood/> ("dood") > - Creating a deployable docker image with Jenkins > <http://activelamp.com/blog/devops/jenkins-build-docker-images/> > - Jenkins building a docker image and sending it to a registry > > <https://medium.com/@gustavo.guss/jenkins-building-docker-image-and-sending-to-registry-64b84ea45ee9> > > After that exploration, you're encouraged to propose a Docker tutorial for > jenkins.io based on your experience. > > Thanks, > Mark Waite > > - <https://www.katacoda.com/courses/jenkins/build-docker-images> > > > On Tue, Feb 4, 2020 at 11:09 AM femiadenubi <femiaden...@gmail.com> wrote: > >> Hello all, please I need help, setting up a jenkins/blueocean container >> to dynamically provision docker agents that are used to build images that >> end up being pushed to an image registry. >> >> I've tried installing and configuring the docker plugin, the docker cloud >> and agent template, but everything I tried does not work. >> >> It's surprising that on the jenkins documentation at jenkins.io, the >> jenkins/blueocean image and the docker:dind images were used to setup >> jenkins, but no single example exist on configuring a docker jenkins slave >> agent that builds a docker image in one of the pipeline stages. >> >> I believe this is a very common step for most pipelines, given the >> ubiquity of running applications as containers. >> >> I would appreciate it, if a step-by-step guide can be provided for this >> scenario to build a maven project. >> >> Thank you for your help. >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Jenkins Users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to jenkinsci-users+unsubscr...@googlegroups.com. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/jenkinsci-users/ec9ff80a-c6e6-434e-b5e0-3e539cf377b7%40googlegroups.com >> <https://groups.google.com/d/msgid/jenkinsci-users/ec9ff80a-c6e6-434e-b5e0-3e539cf377b7%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> > > > -- > Thanks! > Mark Waite > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to jenkinsci-users+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtG1atPtG41GEy5FPyQ_6z%2BnrkLPLX4Qs4xU8QynhVR5%2Bg%40mail.gmail.com > <https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtG1atPtG41GEy5FPyQ_6z%2BnrkLPLX4Qs4xU8QynhVR5%2Bg%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAEHA_ByJXCD0NPwOiW%2BPKsed-Tdxfj-FM2cA1kaUJOBUSeHVJA%40mail.gmail.com.
