We are faced with the same issue for our Jenkins implementation. [email protected] I wonder if you were able to utilize Kaniko or if you found another alternative that worked for you? Any further insight is appreciated!
On Wednesday, October 27, 2021 at 1:15:29 PM UTC-6 [email protected] wrote: > You cannot use the docker.sock anymore > > On Wed, Oct 27, 2021 at 5:00 AM 'Mario Rodriguez' via Jenkins Users < > [email protected]> wrote: > >> and how about if we are using the kubernetes plugin podTemplate >> <https://www.jenkins.io/doc/pipeline/steps/kubernetes/#podtemplate-define-a-podtemplate-to-use-in-the-kubernetes-plugin> >> >> ? more less like this: >> >> podTemplate(cloud: 'kubernetes', label: args.pipelineName, >> containers: getContainers(...), >> volumes: [ >> hostPathVolume(hostPath: '/var/run/docker.sock', mountPath: >> '/var/run/docker.sock'), >> ]) { >> gcloud auth configure-docker --account= >> [email protected] >> docker build --pull -t ${env.btvImageFullName} -t >> ${env.btvLatestFullName} . >> } >> >> On Thursday, September 30, 2021 at 1:32:06 AM UTC-6 [email protected] >> wrote: >> >>> You can use a different builder like Kaniko with the plugin >>> >>> >>> https://github.com/jenkinsci/kubernetes-plugin/blob/master/examples/kaniko-declarative.groovy >>> >>> >>> On Thu, Sep 30, 2021 at 2:05 AM 'Mario Rodriguez' via Jenkins Users < >>> [email protected]> wrote: >>> >>>> Hello, Kubernetes project is planning to deprecate support for >>>> dockershim runtime is version 1.20 and fully drop it in version 1.24 as >>>> indicated here: https://kubernetes.io/blog/2020/12/02/dockershim-faq/ >>>> >>>> >>>> >>>> Reading about the impacts of dockershim removal here: >>>> https://kubernetes.io/docs/tasks/administer-cluster/migrating-from-dockershim/check-if-dockershim-deprecation-affects-you/ >>>> and >>>> here >>>> https://kubernetes.io/docs/tasks/administer-cluster/migrating-from-dockershim/migrating-telemetry-and-security-agents/ >>>> , any >>>> apps that depend on the docker daemon by exposing /var/run/docker.sock >>>> will >>>> be impacted. We use the Kubernetes plugin for Jenkins >>>> <https://plugins.jenkins.io/kubernetes/> using this docker daemon >>>> exposure technique. >>>> >>>> >>>> Assuming a transition from docker to containerd, any idea what changes >>>> will be needed by Kubernetes plugin users to continue working properly ? >>>> >>>> >>>> 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/3b883835-c0bd-49ac-9017-30163ad04a79n%40googlegroups.com >>>> >>>> <https://groups.google.com/d/msgid/jenkinsci-users/3b883835-c0bd-49ac-9017-30163ad04a79n%40googlegroups.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 [email protected]. >> > To view this discussion on the web visit >> https://groups.google.com/d/msgid/jenkinsci-users/1e0e5ccf-5983-4ac3-a806-e23a2801f89en%40googlegroups.com >> >> <https://groups.google.com/d/msgid/jenkinsci-users/1e0e5ccf-5983-4ac3-a806-e23a2801f89en%40googlegroups.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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/aa79afa1-de1a-4bcc-94f9-7f8ab62d730bn%40googlegroups.com.
