hashicorp / docker-hub-images

Automatic builds of container images for Docker Hub
Mozilla Public License 2.0
127 stars 111 forks source link

Packer Docker Hub builds broken #69

Closed danports closed 5 years ago

danports commented 5 years ago

Hi guys, it looks like your Docker Hub builds have been failing for a month or so?

https://hub.docker.com/r/hashicorp/packer/builds/

bengaywins commented 5 years ago

@catsby is there anyone that can work on this? The builds have been failing for over 3 months. The most recent successful build is 1.3.1 while the most recent version of packer is 1.3.4 released a week ago.

Here's the error when I attempt to build the "light" image:

ADD failed: Get https://releases.hashicorp.com/packer/1.3.4/packer_1.3.4_linux_amd64.zip: x509: certificate signed by unknown authority

Corporate proxy seems to caused the above error.

bengaywins commented 5 years ago

Here's the error for the main Dockerfile

can't load package: package app: no buildable Go source files in /go/src/app
The command '/bin/sh -c go-wrapper download' returned a non-zero code: 1

Turns out this is because OnBuild has been deprecated. Maybe this Dockerfile is killed?

And -full

# cd .; git clone https://github.com/mitchellh/gox /go/src/github.com/mitchellh/gox
Cloning into '/go/src/github.com/mitchellh/gox'...
fatal: unable to access 'https://github.com/mitchellh/gox/': SSL certificate problem: unable to get local issuer certificate
package github.com/mitchellh/gox: exit status 128
The command '/bin/sh -c go get github.com/mitchellh/gox' returned a non-zero code: 1

This too is caused by corporate proxy stuff. So not sure why they're failing to build on Dockerhub.

seenickcode commented 5 years ago

@danports, were you able to find a solution to this?

danports commented 5 years ago

It looks like the build pipeline has changed since I opened this issue, since there are no public Packer builds listed on Docker Hub now. I'm guessing they're just docker pushing new images to the Hub now from a private CI system, so this issue is probably obsolete.