Docker Community Forums

Share and learn in the Docker community.

Why does it take so long for the docker hub automated builds to upload the built image?

I’m using the docker hub to automatically build projects hosten on github. What I see from the progress report on the build status page is that the automated builds take a very long time to upload the finished image. It takes much longer for the automated builds to upload the images than it does from my local machine. Sometimes it can take more than 30 minutes!

Is there any way to speed up this? Or is there an alternate build server that can be hooked into Github that is faster?

7 Likes

We’re having the same problem. Incremental automated builds take anywhere from 5 min to 15 min. Any way to speed this up?

+1
We have the same problem.

We gonna get an answer to this? It’s pretty slow and a real pain setting up my prod environment for the first time and I hit bugs.

Slow and free as in beer.

I administer a paying customer account and even small builds take anywhere from 20 min to an hour. It can get randomly jammed for 2-3 hours (!) with no status updates or support response.

I am periodically filing bug reports, but it doesn’t seem to improve.

Yep, we pay as well. So not quite free or beer. It’s not really expensive so how much can we grumble?

If you use automated builds and multiple branches in the same repo, a change in one branch will trigger an automatic rebuild of all images across all branches…slowing everything down further.

Same issue here. Very slow. Can someone from Docker Hub comment on this?

Agree! I’m waiting for 20 minutes and my build not even started!

Automated builds taking 10+ minutes to even kick off. What is the deal?

+1 <a href=“http://miguelgomez.io/devops” target="_blank"rel=“follow”>;)

+1

Same issue, is there a way to fix this?

+1 30+ min so far on a build that takes my small digital ocean droplet 5 min.

+1, very slow, automated builds taking 1 hour

my docker file

FROM python:3.4-slim
    
# STATIC paths for file.
# Don't use flask static. Nginx is your friend
ENV STATIC_URL /static
ENV STATIC_PATH /app/static
    
# Place your flask application on the server
COPY ./app /app
WORKDIR /app

# Install dlib
RUN apt-get -y update
RUN apt-get install -y --fix-missing \
    build-essential \
    cmake \
    gfortran \
    git \
    wget \
    curl \
    graphicsmagick \
    libgraphicsmagick1-dev \
    libatlas-dev \
    libavcodec-dev \
    libavformat-dev \
    libboost-all-dev \
    libgtk2.0-dev \
    libjpeg-dev \
    liblapack-dev \
    libswscale-dev \
    pkg-config \
    python3-dev \
    python3-numpy \
    software-properties-common \
    zip \
    && apt-get clean && rm -rf /tmp/* /var/tmp/*

RUN cd ~ && \
    mkdir -p dlib && \
    git clone -b 'v19.5' --single-branch https://github.com/davisking/dlib.git dlib/ && \
    cd  dlib/ && \
    python3 setup.py install --yes USE_AVX_INSTRUCTIONS

# Install requirements.txt
RUN pip3 install --no-cache-dir -r requirements.txt
    
ENTRYPOINT ["python3"]
CMD ["app.py"]

+1 any update for this. until 2019, the docker build still takes too long for simple image.

FROM alpine:3.6

RUN apk add --no-cache \
  bash \
  curl \
  grep \
  jq

COPY merge-request.sh /usr/bin/

CMD ["merge-request.sh"]

+1 Agreed same issue today.

Automated Docker Hub Builds stuck in pending for longer than I would expect.

Funny to find this thread and see its years old. Keep reading anyway and find posts from hours ago. Same issue here, though it seems to be the case even when manually triggering a build for an image. Yesterday it was working fine. I assume they are just having issues.

Hi there (new paying user here),

i run 2 (public) repos. I decided to start paying with the hope to see some improvement in the build speed.

Apparently no differences in speed if you pay or not.

Yet again, stuck unsure when builds will appear and be usable…happens at least once a month or so, triggers and builds fine, but then just never uploads to hub, PITA tbh.