dapr init hangs when downloading binaries and setting up components

[caioluis]

Expected Behavior

When running dapr init, it should move past the "Downloading binaries and setting up components..." step. Ideally, it should show a progress bar on the downloading steps or tell the user how much time this step usually takes.

In my case, it is hanging for more than an hour. There is this issue #145 where the user takes a long time to finish this step, but eventually gets it to work. I believe a progress bar would be useful in both cases.

Although I have never coded anything like this, I am willing to help with a pull request.

Actual Behavior

❯ dapr init
⌛  Making the jump to hyperspace...
ℹ️  Container images will be pulled from Docker Hub
ℹ️  Installing runtime version 1.14.4
↖  Downloading binaries and setting up components...
Dapr runtime installed to /Users/username/.dapr/bin, you may run the following to add it to your path if you want to run daprd directly:
    export PATH=$PATH:/Users/username/.dapr/bin
↘  Downloading binaries and setting up components...  # <-- hangs here

Steps to Reproduce the Problem

1. On a fresh&successful installation of dapr, run dapr init.
2. It should pull the images from docker and initiate the containers.
3. The "Downloading binaries and setting up components" step should hang.

Release Note

RELEASE NOTE: FIX Dapr init hangs on downloading binaries.

[caioluis]

Apparently, it was due to my VPN being active. I think we can close the issue, but on a side note, I wonder if we can detect and/or set a timeout for this kind of situations. The progress bar suggestion still stands.

[dapr-bot]

This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged (pinned, good first issue, help wanted or triaged/resolved) or other activity occurs. Thank you for your contributions.

[dapr-bot]

This issue has been automatically closed because it has not had activity in the last 37 days. If this issue is still valid, please ping a maintainer and ask them to label it as pinned, good first issue, help wanted or triaged/resolved. Thank you for your contributions.