Docker自动构建会导致意外故障

时间:2014-06-17 00:58:22

标签: build docker auto-build

我正在尝试使用docker创建自动构建。我所做的是将我的bit-bucket repo链接到docker hub并尝试构建。构建状态是意外故障。另外,我看到以下失败消息:

{"错误":"图片取决于未经授权的父母"}

有趣的是,日志说建立成功。


失败消息

[Failure instance: Traceback: <type 'exceptions.RuntimeError'>: HTTP code 400 while uploading     metadata: {"error": "Image depends on an unauthorized parent"}
    /usr/local/lib/python2.7/dist-packages/twisted/internet/defer.py:382:callback
    /usr/local/lib/python2.7/dist-packages/twisted/internet/defer.py:490:_startRunCallbacks
    /usr/local/lib/python2.7/dist-packages/twisted/internet/defer.py:577:_runCallbacks
    /usr/local/lib/python2.7/dist-packages/twisted/internet/defer.py:1155:gotResult
    --- <exception caught here> ---
    /usr/local/lib/python2.7/dist-packages/twisted/internet/defer.py:1097:_inlineCallbacks
    /usr/local/lib/python2.7/dist-    packages/twisted/python/failure.py:389:throwExceptionIntoGenerator
    /app/builder.py:160:execute_job
    /usr/local/lib/python2.7/dist-packages/twisted/internet/defer.py:577:_runCallbacks
    /app/shared/tx/docker.py:295:on_done
    ]

Dockerfile

FROM ubuntu
# make sure the package repository is up to date
RUN echo "deb http://archive.ubuntu.com/ubuntu precise main universe" > /etc/apt/sources.list
RUN apt-get update

# Install vnc, xvfb in order to create a 'fake' display and firefox
RUN apt-get install -y x11vnc xvfb firefox
RUN mkdir /.vnc
# Setup a password
RUN x11vnc -storepasswd 1234 ~/.vnc/passwd
# Autostart firefox (might not be the best way, but it does the trick)
RUN bash -c 'echo "firefox" >> /.bashrc'

EXPOSE 5900
CMD    ["x11vnc", "-forever", "-usepw", "-create"]

日志

Step 0 : FROM ubuntu 
Pulling image (quantal) from ubuntu, endpoint: https://cdn-registry-1.docker.io/v1/ e314931015bd
....
.... 
Removing intermediate container c8e48d27a271 
Step 8 : CMD    ["x11vnc", "-forever", "-usepw", "-create"] 
---> Running in d9319762cb0f 
---> bd7eb37a7f78 
Removing intermediate container d9319762cb0f 
Successfully built bd7eb37a7f78 

1 个答案:

答案 0 :(得分:2)

更新:问题已解决。

我刚从Docker支持团队得到了答案。 这是他们身边的问题,他们已经在调查。

不幸的是,除了等待,你还能做很多事情。