heroku-buildpack-ruby/bundler-1.6.3.tgz - gzip: stdin: unexpected end of file about dokku-alt

[robguthrie]

Sorry if this this not the right repo to post this.. I'm not completely sure what part of the system is failing right now.

[ayufan]

Sure and no problem. I will be glad to help.

Heroku recently started messing with buildpacks by upgrading them to a new
cedar-14 stack. Dokku-alt image on the other side is precompiled, built
when commit is pushed to ITS github repository. You can force to always be
it up to date by forcing custom buildpack. In this case:
https://github.com/heroku/heroku-buildpack-ruby. When building the app,
buildpack will be redownloaded. Try with that first.

Kamil
On Oct 9, 2014 1:04 AM, "Robert Guthrie" [email protected] wrote:

Sorry if this this not the right repo to post this.. I'm not completely
sure what part of the system is failing right now.

—
Reply to this email directly or view it on GitHub
#58 (comment).

[robguthrie]

Thanks for the quick response @ayufan. I'm finding that when I set a BUILDPACK_URL the process seems to hang on Fetching custom buildpack. Should it take a very long time? IE: more than 5 minutes? (I'm using a VPS on Digital Ocean.. and have tried a few build packs)

Also I'm not entirely sure about what a valid buildpack url is. I see some people reference the url like you did: https://github.com/heroku/heroku-buildpack-ruby and some append .git on the end: https://github.com/heroku/heroku-buildpack-ruby.git which is the right format?

[ayufan]

Both of them are just right. No it shouldn't be. How it works for you from
command line? Maybe you have some problems with connectivity in containers?
Try to spawn shell to test it:

docker run -i -t ayufan/dokku-alt-buildstep:foreman /bin/bash

And execute git and curl command in it.
On Oct 9, 2014 1:24 AM, "Robert Guthrie" [email protected] wrote:

Thanks for the quick response @ayufan https://github.com/ayufan. I'm
finding that when I set a BUILDPACK_URL the process seems to hang on
Fetching custom buildpack. Should it take a very long time? IE: more than 5
minutes? (I'm using a VPS on Digital Ocean.. and have tried a few build
packs)

Also I'm not entirely sure about what a valid buildpack url is. I see some
people reference the url like you did:
https://github.com/heroku/heroku-buildpack-ruby and some append .git on
the end: https://github.com/heroku/heroku-buildpack-ruby.git which is the
right format?

—
Reply to this email directly or view it on GitHub
#58 (comment).

[robguthrie]

You're on to it.

oot@21e1dc3058e1:/# wget https://s3-external-1.amazonaws.com/heroku-buildpack-ruby/bundler-1.6.3.tgz
--2014-10-08 23:31:39--  https://s3-external-1.amazonaws.com/heroku-buildpack-ruby/bundler-1.6.3.tgz
Resolving s3-external-1.amazonaws.com (s3-external-1.amazonaws.com)... failed: Temporary failure in name resolution.
wget: unable to resolve host address `s3-external-1.amazonaws.com'

root@21e1dc3058e1:/# git clone https://github.com/heroku/heroku-buildpack-ruby
Cloning into 'heroku-buildpack-ruby'...
error: Couldn't resolve host 'github.com' while accessing https://github.com/heroku/heroku-buildpack-ruby/info/refs
fatal: HTTP request failed

This is my resolv.conf inside the container..

root@21e1dc3058e1:/# cat /etc/resolv.conf 
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
#     DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 2001:4860:4860::8844
nameserver 2001:4860:4860::8888
nameserver 8.8.8.8

Maybe I should disable ipv6?

[ayufan]

You can do it or you can force to use custom DNS in /etc/default/docker.
Maybe it helps.
On Oct 9, 2014 1:33 AM, "Robert Guthrie" [email protected] wrote:

You're on to it.

oot@21e1dc3058e1:/# wget https://s3-external-1.amazonaws.com/heroku-buildpack-ruby/bundler-1.6.3.tgz
--2014-10-08 https://s3-external-1.amazonaws.com/heroku-buildpack-ruby/bundler-1.6.3.tgz--2014-10-08 23:31:39-- https://s3-external-1.amazonaws.com/heroku-buildpack-ruby/bundler-1.6.3.tgz
Resolving s3-external-1.amazonaws.com (s3-external-1.amazonaws.com)... failed: Temporary failure in name resolution.
wget: unable to resolve host address `s3-external-1.amazonaws.com'

root@21e1dc3058e1:/# git clone https://github.com/heroku/heroku-buildpack-ruby
Cloning into 'heroku-buildpack-ruby'...
error: Couldn't resolve host 'github.com' while accessing https://github.com/heroku/heroku-buildpack-ruby/info/refs
fatal: HTTP request failed

This is my resolv.conf inside the container..

root@21e1dc3058e1:/# cat /etc/resolv.conf

Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)

DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN

nameserver 2001:4860:4860::8844
nameserver 2001:4860:4860::8888
nameserver 8.8.8.8

Maybe I should disable ipv6?

—
Reply to this email directly or view it on GitHub
#58 (comment).

[robguthrie]

Thanks for all your help @ayufan. Disabling ipv6 worked around my issues. Really really appreciate your quick and useful help. :)