阅读背景:

Docker图像注册表/存储库在私有cloudfoundry上

来源:互联网 

I installed Cloudfoundry (approximately version v220) on OpenStack and I want to work with private Docker images on Cloudfoundry.

我在OpenStack上安装了Cloudfoundry(大约版本为v220),我想在Cloudfoundry上使用私有Docker镜像。

I would like to run docker registry/repository (Doc|Github) server on Cloudfoundry.

我想在Cloudfoundry上运行docker registry / repository(Doc | Github)服务器。

  1. I found tutorials on how to install it directly on a machine/VM (1|2|3).
    • Is there something to be said against running it on Cloudfoundry?
    • 在Cloudfoundry上运行它有什么可说的吗?
    • How do I install it?
    • 我该如何安装?
  2. 我找到了关于如何直接在机器/ VM上安装它的教程(1 | 2 | 3)。在Cloudfoundry上运行它有什么可说的吗?我该如何安装?
  3. Is Diego or something like that already providing the registry/repository service?
  4. 迭戈或类似的东西已经提供注册表/存储库服务?
  5. I thought Diego was part of Cloudfoundry but reading the CF release notes it looks like I have to install Diego separately is that correct (see "Recommended Diego Version")?
  6. 我认为Diego是Cloudfoundry的一部分,但是阅读CF发行说明看起来我必须单独安装Diego是正确的(参见“推荐的迭戈版本”)?

1 个解决方案

#1


2  

It is possible to run private Docker images on Cloudfoundry and there is a CF-specific registry you can use. In order to do that, there are a number of extra steps that you will need to undertake.

可以在Cloudfoundry上运行私有Docker镜像,并且可以使用特定于CF的注册表。为此,您需要执行许多额外步骤。

To answer your last question first, we must tease apart what exactly is meant by "Diego is a part of Cloud Foundry". Cloud Foundry is deployed using BOSH, which among other things has a concept of a release. A release is in essence a versioned collection of source code, configuration, dependencies, etc. that your system needs to run. I would recommend reading the BOSH docs to gain more of an understanding as to exactly what BOSH is.

为了首先回答你的上一个问题,我们必须分开“迭戈是Cloud Foundry的一部分”究竟是什么意思。 Cloud Foundry使用BOSH进行部署,其中包括发布的概念。发行版本质上是系统需要运行的源代码,配置,依赖项等的版本化集合。我建议阅读BOSH文档以获得更多关于BOSH究竟是什么的理解。

Historically, Cloud Foundry has been made up of a single BOSH release, cf-release, but that is no longer the case. Diego itself is deployed as a separate release, diego-release, and that is what is being referred to in the cf-release release notes. To ensure compatibility, each release of cf-release publishes which release of diego-release is being run alongside.

从历史上看,Cloud Foundry由单个BOSH版本cf-release组成,但现在已经不再如此。 Diego本身作为一个单独的版本,diego-release部署,这就是cf-release发行说明中提到的内容。为了确保兼容性,cf-release的每个版本都会发布哪个版本的diego-release正在运行。

Diego does support an internal docker registry that can run private docker images, but in order to do so, you must deploy another BOSH release and configure it correctly. That bosh release is the diego-docker-cache-release, the README should hopefully help in getting you started. This cf-dev post by the current Diego PM might also be helpful in setting it up. If you run into any problems or issues, I would recommend posting to the cf-dev mailing lists as the CF community and developers maintain a closer watch on that communication channel.

Diego确实支持可以运行私有docker镜像的内部docker注册表,但为了做到这一点,你必须部署另一个BOSH版本并正确配置它。那个波什版本是diego-docker-cache-release,README应该有助于你开始。当前Diego PM的这篇cf-dev帖子也可能有助于设置它。如果您遇到任何问题或问题,我建议发布到cf-dev邮件列表,因为CF社区和开发人员密切关注该通信渠道。


分享到: