Re: Kubernetes plugin for Jenkins after dockershim runtime is deprecated

[Ivan Fernandez Calvo]

Another solution that does not impact your pipelines, is to use a DinD 
container and export DOCKER_HOST in all the containers of the pod, this 
allows access to Docker to all containers using the docker CLI

pipeline {
  agent {
  kubernetes {
defaultContainer 'docker-cli'
yaml '''
  apiVersion: v1
  kind: Pod
  spec:
imagePullSecrets:
  - name: 'repo.example.com'
  - name: 'repo1.example.com'
containers:
  - name: dind
image: docker:20.10.12-dind
securityContext:
  privileged: true
env:
  - name: DOCKER_TLS_CERTDIR
value: ""
command:
  - dockerd
args:
  - -H tcp://localhost:2375
  --H unix:///var/run/docker.sock
ports:
  - containerPort: 2375
hostIP: 127.0.0.1
volumeMounts:
  - name: docker-cache
mountPath: /var/lib/docker
  - name: docker-cli
image: my-docker-cli-container:latest
command:
  - sleep
args:
  - infinity
env:
  - name: DOCKER_HOST
value: tcp://localhost:2375
volumes:
  - name: docker-cache
emptyDir: {}
'''
}
}


El miércoles, 13 de abril de 2022 a las 1:21:17 UTC+2, janmont...@gmail.com 
escribió:

> For builds that need docker, we have used docker:dind in the past. So we 
> have a maven build running in a maven container in a pod, and that build 
> uses dind to run testcontainers. 
>
> I wonder if something like that would work for your use case?
>
> Here’s more info on dind: 
>
> http://blog.teracy.com/2017/09/11/how-to-use-docker-in-docker-dind-and-docker-outside-of-docker-dood-for-local-ci-testing/
>
> On Wed, Sep 29, 2021 at 19:05 'Mario Rodriguez' via Jenkins Users <
> jenkins...@googlegroups.com> 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 
>>  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 jenkinsci-use...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-users/3b883835-c0bd-49ac-9017-30163ad04a79n%40googlegroups.com
>>  
>> 
>> .
>>
>

-- 
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/0d79c6f8-a868-41d7-854f-0350edf67db8n%40googlegroups.com.

Re: Kubernetes plugin for Jenkins after dockershim runtime is deprecated

[Jan Monterrubio]

For builds that need docker, we have used docker:dind in the past. So we
have a maven build running in a maven container in a pod, and that build
uses dind to run testcontainers.

I wonder if something like that would work for your use case?

Here’s more info on dind:
http://blog.teracy.com/2017/09/11/how-to-use-docker-in-docker-dind-and-docker-outside-of-docker-dood-for-local-ci-testing/

On Wed, Sep 29, 2021 at 19:05 'Mario Rodriguez' via Jenkins Users <
jenkinsci-users@googlegroups.com> 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
>  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 jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/3b883835-c0bd-49ac-9017-30163ad04a79n%40googlegroups.com
> 
> .
>

-- 
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/CADgiF9JZ3Sbf3fYsMsJscWcDU0Kru9Oyk%2B2XzRfv40JzWuk%2BOA%40mail.gmail.com.

Re: Kubernetes plugin for Jenkins after dockershim runtime is deprecated

['Mario Rodriguez' via Jenkins Users]

Hi, yes, I was able to replace docker tooling with a combination of kaniko 
and podman.  Kaniko will build the OCI container images in a daemonless 
fashion and podman will let you run other commands such as tag, pull, push. 
 Please be aware kaniko 1.7.0 has issues with workload identity 
authentication and 1.8.0 has issues with public gcr.io repositories, then 
1.6.0 is the latest stable version that works fine under broader conditions.

I hope it helps

On Tuesday, April 12, 2022 at 4:14:12 AM UTC-6 sri...@ftdi.com wrote:

> We are faced with the same issue for our Jenkins implementation. 
> cr...@llbean.com 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 car...@apache.org 
> wrote:
>
>> You cannot use the docker.sock anymore
>>
>> On Wed, Oct 27, 2021 at 5:00 AM 'Mario Rodriguez' via Jenkins Users <
>> jenkins...@googlegroups.com> wrote:
>>
>>> and how about if we are using the kubernetes plugin podTemplate 
>>> 
>>>  
>>> ?  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=
>>> jen...@myproject.iam.gserviceaccount.com
>>>docker build --pull -t ${env.btvImageFullName} -t 
>>> ${env.btvLatestFullName} . 
>>> }
>>>
>>> On Thursday, September 30, 2021 at 1:32:06 AM UTC-6 car...@apache.org 
>>> 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 <
 jenkins...@googlegroups.com> 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 
>  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 jenkinsci-use...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-users/3b883835-c0bd-49ac-9017-30163ad04a79n%40googlegroups.com
>  
> 
> .
>
 -- 
>>> 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-use...@googlegroups.com.
>>>
>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/jenkinsci-users/1e0e5ccf-5983-4ac3-a806-e23a2801f89en%40googlegroups.com
>>>  
>>> 
>>> .
>>>
>>

-- 
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/a266480f-d623-4d72-9f56-98bf7f3545dan%40googlegroups.com.

Re: Kubernetes plugin for Jenkins after dockershim runtime is deprecated

[Steve Ridley]

We are faced with the same issue for our Jenkins implementation. 
cr...@llbean.com 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 car...@apache.org wrote:

> You cannot use the docker.sock anymore
>
> On Wed, Oct 27, 2021 at 5:00 AM 'Mario Rodriguez' via Jenkins Users <
> jenkins...@googlegroups.com> wrote:
>
>> and how about if we are using the kubernetes plugin podTemplate 
>> 
>>  
>> ?  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=
>> jen...@myproject.iam.gserviceaccount.com
>>docker build --pull -t ${env.btvImageFullName} -t 
>> ${env.btvLatestFullName} . 
>> }
>>
>> On Thursday, September 30, 2021 at 1:32:06 AM UTC-6 car...@apache.org 
>> 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 <
>>> jenkins...@googlegroups.com> 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 
  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 jenkinsci-use...@googlegroups.com.
 To view this discussion on the web visit 
 https://groups.google.com/d/msgid/jenkinsci-users/3b883835-c0bd-49ac-9017-30163ad04a79n%40googlegroups.com
  
 
 .

>>> -- 
>> 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-use...@googlegroups.com.
>>
> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-users/1e0e5ccf-5983-4ac3-a806-e23a2801f89en%40googlegroups.com
>>  
>> 
>> .
>>
>

-- 
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/aa79afa1-de1a-4bcc-94f9-7f8ab62d730bn%40googlegroups.com.

Re: Kubernetes plugin for Jenkins after dockershim runtime is deprecated

[Carlos Sanchez]

You cannot use the docker.sock anymore

On Wed, Oct 27, 2021 at 5:00 AM 'Mario Rodriguez' via Jenkins Users <
jenkinsci-users@googlegroups.com> wrote:

> and how about if we are using the kubernetes plugin podTemplate
> 
> ?  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=
> jenk...@myproject.iam.gserviceaccount.com
>docker build --pull -t ${env.btvImageFullName} -t
> ${env.btvLatestFullName} .
> }
>
> On Thursday, September 30, 2021 at 1:32:06 AM UTC-6 car...@apache.org
> 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 <
>> jenkins...@googlegroups.com> 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
>>>  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 jenkinsci-use...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/jenkinsci-users/3b883835-c0bd-49ac-9017-30163ad04a79n%40googlegroups.com
>>> 
>>> .
>>>
>> --
> 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/1e0e5ccf-5983-4ac3-a806-e23a2801f89en%40googlegroups.com
> 
> .
>

-- 
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/CALHFn6M1RSsy%3D1-Xhwk_YocX-1kMASY03x5Uuvgpa1qG%3DYOhhQ%40mail.gmail.com.

Re: Kubernetes plugin for Jenkins after dockershim runtime is deprecated

['Mario Rodriguez' via Jenkins Users]

and how about if we are using the kubernetes plugin podTemplate 

 
?  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=jenk...@myproject.iam.gserviceaccount.com
   docker build --pull -t ${env.btvImageFullName} -t 
${env.btvLatestFullName} . 
}

On Thursday, September 30, 2021 at 1:32:06 AM UTC-6 car...@apache.org 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 <
> jenkins...@googlegroups.com> 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 
>>  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 jenkinsci-use...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-users/3b883835-c0bd-49ac-9017-30163ad04a79n%40googlegroups.com
>>  
>> 
>> .
>>
>

-- 
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/1e0e5ccf-5983-4ac3-a806-e23a2801f89en%40googlegroups.com.

Re: Kubernetes plugin for Jenkins after dockershim runtime is deprecated

[Carlos Sanchez]

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 <
jenkinsci-users@googlegroups.com> 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
>  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 jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/3b883835-c0bd-49ac-9017-30163ad04a79n%40googlegroups.com
> 
> .
>

-- 
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/CALHFn6PM8h%2Bg7ZhS3hPeO1nHBjW2X0QO6RHTDJmaE5fLNjLjVw%40mail.gmail.com.

Kubernetes plugin for Jenkins after dockershim runtime is deprecated

['Mario Rodriguez' via Jenkins Users]

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 
 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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/3b883835-c0bd-49ac-9017-30163ad04a79n%40googlegroups.com.