Cant reproduce docker build

[mementor]

Hi,

I want to rebuild docker image by myself like this:

caddy-docker:master ✓ ➭ docker build --no-cache=true -t caddytest .
Sending build context to Docker daemon 165.4 kB
Step 1 : FROM alpine:3.2
 ---> d6ead20d5571
Step 2 : MAINTAINER Abiola Ibrahim <abiola89@gmail.com>
 ---> Running in e402e0822682
 ---> a8fd5f89bae8
Removing intermediate container e402e0822682
Step 3 : LABEL caddy_version "0.8" architecture "amd64"
 ---> Running in bec50acb46d3
 ---> bd13eec6afe3
Removing intermediate container bec50acb46d3
Step 4 : RUN apk add --update openssh-client git tar
 ---> Running in cc3b2d9b0f10
fetch http://dl-4.alpinelinux.org/alpine/v3.2/main/x86_64/APKINDEX.tar.gz
(1/15) Installing run-parts (4.4-r0)
(2/15) Installing openssl (1.0.2e-r0)
(3/15) Installing lua5.2-libs (5.2.4-r0)
(4/15) Installing lua5.2 (5.2.4-r0)
(5/15) Installing ncurses-terminfo-base (5.9-r3)
(6/15) Installing ncurses-widec-libs (5.9-r3)
(7/15) Installing lua5.2-posix (33.3.1-r2)
(8/15) Installing ca-certificates (20141019-r2)
(9/15) Installing libssh2 (1.5.0-r0)
(10/15) Installing curl (7.42.1-r0)
(11/15) Installing expat (2.1.0-r1)
(12/15) Installing pcre (8.37-r1)
(13/15) Installing git (2.4.1-r0)
(14/15) Installing openssh-client (6.8_p1-r4)
(15/15) Installing tar (1.28-r0)
Executing busybox-1.23.2-r0.trigger
Executing ca-certificates-20141019-r2.trigger
OK: 26 MiB in 30 packages
 ---> 3273f1881310
Removing intermediate container cc3b2d9b0f10
Step 5 : RUN mkdir /caddysrc && curl -sL -o /caddysrc/caddy_linux_amd64.tar.gz "http://caddyserver.com/download/build?os=linux&arch=amd64&features=git" && tar -xf /caddysrc/caddy_linux_amd64.tar.gz -C /caddysrc && mv /caddysrc/caddy /usr/bin/caddy && chmod 755 /usr/bin/caddy && rm -rf /caddysrc && printf "0.0.0.0\nbrowse" > /etc/Caddyfile
 ---> Running in 0a07b399743c
 ---> 2dc36f69ef3b
Removing intermediate container 0a07b399743c
Step 6 : RUN mkdir /srv
 ---> Running in e6810d635e75
 ---> c84590abf9ef
Removing intermediate container e6810d635e75
Step 7 : EXPOSE 2015
 ---> Running in d4c5fa86a59e
 ---> a363a3fa2473
Removing intermediate container d4c5fa86a59e
Step 8 : EXPOSE 443
 ---> Running in 99f368230894
 ---> b54375eda9e1
Removing intermediate container 99f368230894
Step 9 : EXPOSE 80
 ---> Running in e257eb6f71ee
 ---> 86b479f70fc7
Removing intermediate container e257eb6f71ee
Step 10 : WORKDIR /srv
 ---> Running in e80b958c5ace
 ---> c138f2b10bba
Removing intermediate container e80b958c5ace
Step 11 : ENTRYPOINT /usr/bin/caddy
 ---> Running in 657d63f28087
 ---> e26078730911
Removing intermediate container 657d63f28087
Step 12 : CMD --conf /etc/Caddyfile
 ---> Running in ea5f8c3b094e
 ---> 0ac0949135bd
Removing intermediate container ea5f8c3b094e
Successfully built 0ac0949135bd

But when start container -- I get error:

caddy-docker:master ✓ ➭ docker run -d -v /tmp/sharer:/srv -p 80:80 -p 443:443 caddytest
21e1969881a61e6953e8a05d8cc2742663243a69b475761cb1eddccb91b24625
Error response from daemon: Cannot start container 21e1969881a61e6953e8a05d8cc2742663243a69b475761cb1eddccb91b24625: [8] System error: no such file or directory

Some googling get me this issue moby/moby#14972
It refers to rebuild binary to statically linked, but in Dockerfile in this repo it just downloads prepared binary from caddyserver.com

In same time image pulled from docker hub works fine:

➭ docker run -d -v /tmp/sharer:/srv -p 80:2015 abiosoft/caddy       
a675879b2ec65a277d4af35efe943b0c1a4c2909b210a6666f0a0ac81a469c3d
➭ docker ps
CONTAINER ID        IMAGE               COMMAND                  CREATED             STATUS              PORTS                                   NAMES
a675879b2ec6        abiosoft/caddy      "/usr/bin/caddy --con"   5 seconds ago       Up 4 seconds        80/tcp, 443/tcp, 0.0.0.0:80->2015/tcp   jolly_easley

Please, can you show instructions to reproduce working image?

[abiosoft]

This is due to an issue with Caddy's download server temporarily not producing static binary. This should be okay in 24 hours.

[abiosoft]

You should be able to reproduce it now.

Feel free to close this issue when you confirm.

Thanks.