# Jenkins plugins update

**URL:** <https://community.jenkins.io/t/jenkins-plugins-update/15469>\
**Category:** Ask a question\
**Tags:** question\
**Created:** [May 26, 2024, 7:38pm UTC](https://community.jenkins.io/t/jenkins-plugins-update/15469 "2024-05-26T19:38:22Z")\
**Posts on this page:** 1\
**Showing post:** 27

<div class="post-metadata">

**Author:** ![MarkEWaite](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/markewaite/32/20_2.png) [@MarkEWaite](https://community.jenkins.io/u/MarkEWaite)\
**Post date:** [June 4, 2024, 2:56pm UTC](https://community.jenkins.io/t/jenkins-plugins-update/15469/27 "2024-06-04T14:56:35Z")

</div>

> [@arafata](#):
>
> you need to mount docker binary when launching container -v /var/run/docker.sock:/var/run/docker.sock

Mounting the Docker socket into the controller image is a mistake for two reasons.

1. Running Jenkins jobs on the controller is a mistake. Use agents to run Jenkins jobs. The [controller isolation section](https://www.jenkins.io/doc/book/security/controller-isolation/) in the [“Securing Jenkins” chapter](https://www.jenkins.io/doc/book/security/) of the documentation describes the security risks of running jobs on the controller
2. Mounting the Docker socket in the container image is a mistake. A [stackoverflow article](https://stackoverflow.com/questions/40844197/what-is-the-docker-security-risk-of-var-run-docker-sock) describes the security risks of mounting the Docker socket in a container

> [@arafata](#):
>
> there is no caching when rebuilding an image

When I build images, the layers that do not change are cached. I don’t know what configuration you use to build container images, but if the layers are not cached in your configuration, then you need to fix that configuration. Layer caching is a standard part of the `docker build` process.

---

_[View the full topic](https://community.jenkins.io/t/jenkins-plugins-update/15469)._