Docker Hub超时自动构建 [英] Docker Hub timeout in automated build

问题描述

我正在使用自动化版本为基准套件创建泊坞窗图像。在其中一个基准测试中，即网页搜索，我必须使用非常大的索引文件（11GB）。我的图像没有被构建，我收到这个错误：构建已超时。

I'm using automated build to create docker images for a benchmark suite. In one of the benchmarks, which is web search, I have to use a very big index file (11GB). My image is not being built, and I'm receiving this error :The build has timed out.

但是当我检查构建日志，这是很长的时候，在最后一行我可以看到它已经成功建成：成功构建4c84c7ec04c6

But when I check the build log, which is very long, in the last line I can see that it has actually built successfully: Successfully built 4c84c7ec04c6

似乎负责创建此映像的工作人员在处理和构建映像时失去与其主（注册表节点）的连接。这可能是因为需要几个小时才能下载索引文件。

It seems that the worker responsible for creating this image, loses its connection with its master (registry node), while it is still processing and building the image. It's probably due to the fact that it takes a couple of hours to download the index file.

我可以做些什么来防止这种情况发生？

What can I do to prevent this from happening?

有关详细信息，可以查看构建日志这里。

For more information, you can check the build log here.

谢谢。

推荐答案

我们已经联系了他们的支持团队，根据他们的回应，目前对自动构建的限制是：

I've contacted their support team, and according to their response, the current limits on Automated Builds are:

• 2小时


• 2 GB RAM


• 1 CPU


• 30 GB磁盘空间

• 2 hours
• 2 GB RAM
• 1 CPU
• 30 GB Disk Space

因此，对于较大的版本，您必须将其分解成由 FROM 语句和存储库链接连接的多个自动构建，或在本地构建在您的机器上，并将其推送到存储库。

So, for larger builds you have to either break them into several Automated Builds connected by FROM statements and Repository Links, or build them locally on your machine and push them to the repository.

这篇关于Docker Hub超时自动构建的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！