Hacker News Reader

Comment by druiid | Hacker News Reader

It appears that download issues with the ruby buildpack still aren't fixed. Really you guys should be hosting these on your own S3 account as literally every time I've tried to use Flynn or Deis they are unusable because both utilities use heroku hosted buildpacks and they're consistently broken (slugbuilder related I think?).

View on HN

We're tracking this issue at https://github.com/flynn/flynn/issues/85

To date we've tried to push fixes upstream to buildpacks so that we can avoid the maintenance burden of keeping forks up-to-date.

What download issues do you speak of? They work great in Deis' test infrastructure: http://ci.deis.io/view/example-apps/job/test-integration-rub...

-----> Ruby app detected ! ! Command: 'set -o pipefail; curl --fail --retry 3 --retry-delay 1 --connect-timeout 3 --max-time 30 https://s3-external-1.amazonaws.com/heroku-buildpack-ruby/bu... -s -o - | tar zxf - ' failed unexpectedly: ! ! gzip: stdin: unexpected end of file ! tar: Child returned status 1 ! tar: Error is not recoverable: exiting now

I opened an issue request with Deis a while back for the same problem and they reported it being an upstream issue with slugbuilder.

Edit: Heh, apparently we already talked about this https://github.com/deis/deis/issues/1016

Yep. It was because slugbuilder didn't lock buildpacks to a known working version when you ran a `docker build`. It always pulled master, which may or may not work. We fixed that up, and we're in sync with Heroku's buildpack version that's running in prod now: https://github.com/deis/slugbuilder/blob/deis/builder/instal...

Didn't notice the issue get closed. Thanks! I'll re-install Deis again :D

Reply on news.ycombinator.com