我正在与Diego探索Cloud Foundry及其Docker支持。我的问题是：是否可以像以前一样部署jar（使用ResultSetMetaData，提供有关jar位置，buildpack和要使用的堆栈的信息）并让CF构建一个（Docker？）容器，就像它一样曾经与DEA有关，或者是否有必要始终为CF提供现成的Docker镜像来构建容器？如果老了＆＃39;方式仍然支持，以这种方式使用Diego是一个好主意，还是我们都应该转向Docker？
答案 0 :(得分：1)
Cloud Foundry's Diego runtime continues to support buildpack deployments, where it will create the container and the runtime artifacts needed to run your application. The container it creates is not a Docker container. For example, Pivotal Cloud Foundry creates a Garden-RunC container.
Docker support can be useful when you have a prepackaged Docker image that you would like to deploy without modification, but the buildpack approach is still preferred when you have a choice.
Buildpacks will simplify the role of both the developer and the IT operator when using Cloud Foundry. With buildpacks, the developer is no longer responsible for design and maintenance of the Dockerfile, and other concerns that are not directly related to application development.
The IT operator gets complete consistency in terms of versioning and patch levels for the OS and runtimes across all buildpack containers. They also have the ability to perform automated, zero-downtime patches and upgrades that are deployed across all buildpack containers in the Cloud Foundry environment. This is a very powerful tool, both for security and efficiency.