Thanks for the answer. I was precisely trying to avoid maintaining a custom image just for the certificates, but if I don't have a choice, I'll go with it.
On Sunday, October 9, 2016 at 12:42:02 PM UTC-4, Victor Martinez wrote: > > If I understood correctly you don't need to custom anything but using the > FROM instruction in your Dockerfile to specify what Jenkins official image > you would like to use and on the top of it you can set your certificates > accordingly: > > FROM jenkins:2.19.1 > COPY whatever_credentials /whatever_location > > That's the advantage of using docker, reusing someone else's images and > specify your configuration by using the other docker instructions. It's > worth using some SCM tool to track any changes in your Dockerfile. > > Cheers > > > On Sunday, 9 October 2016 16:43:50 UTC+1, sleipnir wrote: >> >> Hi there >> >> I am using the official jenkins image available here >> https://hub.docker.com/_/jenkins/ and everything is fine so far. >> But in order to run my builds I need to install some self-signed >> certificates to access some internal servers, and I would rather keep using >> the default image and not create a custom one. >> >> What would be the proper clean way to tell the jenkins image to install >> my certificates ? >> >> Thanks >> >> >> >> >> -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/9440eb9f-ed02-40d1-b48f-4bb7d2f38f7b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
