it means a build with some "malicious code" (sic) could access all other builds, secrets injected into a build environment by jenkins, all host ressources, etc. It could as well create by intent or because of some buggy script create thousands containers and exhaust host resources.
consider docker.sock as some super-root access to your build node. 2017-07-10 17:45 GMT+02:00 Yakobe <jakewbis...@gmail.com>: > The security of these jenkins builds are not critical since they are just > for testing. Therefore it sounds perhaps a simpler approach. > However, i'm interested in what the issues are with build isolation. Does > that mean that build could fail, and under what sort of circumstance? > > -- > 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/6fadf55e-ccff-4e9a-951b-8e9731e8c01a%40googlegroups. > com > <https://groups.google.com/d/msgid/jenkinsci-users/6fadf55e-ccff-4e9a-951b-8e9731e8c01a%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- 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/CANMVJzkm%2BJFqFKROs-0%2BgNM9ovo-ThT0zSF%3DrtRxe9PS5D51uQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
