We are using the Kubernetes plugin to spawn agents whenever we need them.
Each of the agents has two build slots.
In our pipelines, we use
```
stage('Service')
*{ *agent
*{ *docker
*{ *image 'quay.io/....'
*} }*
```
to be flexible in the build image in each step. This causes that here, the
openjdk image is spawned within the agent created with the Kubernetes
plugin, that again is a running container in Kubernetes.
Since we also use docker and jib in our pipelines, these tools as started
with the the docker in docker images (see example above, it would be an
openjdk image).
Now we are facing the Kubernetes feature to remove docker from Kubernetes.
In our current situation, the docker socket is mounted to the agents
running in the pod and therefore we could use docker there. With Kubernetes
19, this will not be possible any longer.
Do you have any suggestions or hints how to solve this without redesigning
all of our pipelines?
--
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/f08c22a0-df0c-4c42-aa98-1b4a1318977en%40googlegroups.com.
