I think I made a mistake in JENKINS-49864 where I put the Docker binaries under /usr/local/bin and then with JENKINS-50195 it's now impossible for the evergreen-client to upgrade.
So IMO we must:
- fix it so that Docker binaries are user accessible?
- define a common way to handle those binaries? For instance putting them all under /evergreen/bin and define a standard way to download/install them? Maybe this should actually be handled using the BOM and upgraded/downloaded like anything else?
WDYT rtyler?
- relates to
-
JENKINS-49866 Automatically configure Docker Cloud if a Docker host is available
-
- Resolved
-
Update on this: we had some discussions around this with rtyler, and hence I am going to close this at least for now.
We do have a few components that require an explicit Docker pull of the last image and run anew on the same volume (another example is the embedded Nginx reverse proxy).
For now, again, we consider this a non-issue and an acceptable tradeoff wrt. update complexity. We obviously put in this category components that we expect to not change often.