Heroku CLI hangs when installed within a docker container

[lox]

When trying to install the Heroku CLI in a docker container, it seems to hang at:

Installing Heroku Toolbelt v4... done.
For more information on Toolbelt v4: https://github.com/heroku/heroku-cli
heroku-cli: Adding dependencies... done
heroku-cli: Installing core plugins...

Indefinitely. Using an ubuntu:14.04 base image and installing with:

RUN wget -O- https://toolbelt.heroku.com/install-ubuntu.sh | sh \
  && heroku plugins:install heroku-docker

Any ideas?

My docker file looks like:

FROM ubuntu:14.04
RUN apt-get update -y && apt-get install -y wget
RUN wget -O- https://toolbelt.heroku.com/install-ubuntu.sh | sh \
  && heroku plugins:install heroku-docker

I'm running this within another docker container in our CI environment (Buildkite).

[lox]

I've isolated this down to the heroku plugins:install heroku-docker stanza, once it's in the node subprocess. The strace output doesn't yield much.

[lox]

This also fails in the docker hub automated build process (see https://hub.docker.com/r/99designs/heroku-cli/):

�[91mInstalling Heroku Toolbelt v4...�[0m�[91m !    Heroku client internal error.
 !    Search for help at: https://help.heroku.com
 !    Or report a bug at: https://github.com/heroku/heroku/issues/new

    Error:       connect timeout reached (Excon::Errors::Timeout)
    Command:     heroku plugins:install heroku-docker
    Version:     heroku-toolbelt/3.42.21 (x86_64-linux) ruby/1.9.3
    Error ID:    dc8071b0a43a43b5b44cbb2536555a61


    More information in /root/.heroku/error.log

�[0mRemoving intermediate container e5e747b5adc0

[ransombriggs]

Both of these problems were a temporary problem that some users encountered this morning. The other users affected had these problems resolve when they retried the commands. Could you please retry and let me know if things pass now?

[jdx]

is it pausing for 60 seconds before you get that connection timeout message? can you run curl https://cli-assets.heroku.com/master/manifest.json?

[lox]

Yup, fixed. Thanks all.