`--image-registry` during `dapr init` not fully offline

[atrauzzi]

Expected Behaviour

Offline Dapr installation with --image-registry to not attempt to reach out over the network.

Actual Behaviour

⌛  Making the jump to hyperspace...
⚠  Flag --image-registry is a preview feature and is subject to change.
⚠  Failed to get runtime version: 'Get "https://api.github.com/repos/dapr/dapr/releases": dial tcp: lookup api.github.com on 127.0.0.53:53: server misbehaving'. Trying secondary source
❌  cannot get the latest release version: 'Get "https://dapr.github.io/helm-charts/index.yaml": dial tcp: lookup dapr.github.io on 127.0.0.53:53: server misbehaving'. Try specifying --runtime-version=<desired_version>

Appears to try going out over the network to grab helm charts?

Steps to Reproduce the Problem

• Grab a standalone Dapr installation
• Disable networking (disable wifi/disconnect ethernet/disable interfaces)
• Extract the standalone installation
• Navigate to the directory in a terminal
• Run the following:

./dapr init --image-registry=localhost

You'll get something similar to the actual behaviour section above.

Additional Note

❯ ./dapr init --image-registry=localhost --from-dir=./
⌛  Making the jump to hyperspace...
❌  both --image-registry and --from-dir flags cannot be given at the same time

--from-dir can't be used in combination with --image-registry. Potentially some ambiguity around what constitutes an offline install.

Release Note

RELEASE NOTE: FIX Using an image registry no longer attempts to reach out over the network.