Registry credentials with "https://registry_address" address doesn’t work

Expected Behavior

When using “https://***.azurecr.io” as registry address, edgeagent should be able to authenticate and pull image successfully as docker login accepts such kind of address. Here’s a sample config snippet in deployment.json (removed password):

"registryCredentials": {
              "chaoyitest": {
                "username": "chaoyitest",
                "password": "…",
                "address": "https://chaoyitest.azurecr.io"
              }
            }

Current Behavior

Edgeagent cannot pull image from private registry with unauthorized error.

Steps to Reproduce

1. Create a new Edge device
2. Make sure the address in registryCredentials has “https://” header and there’re modules from the private registry
3. Deploy the deployment.json to the new Edge device
4. Check iotedge logs

Context (Environment)

Device (Host) Operating System

I created a VM using Ubuntu Server 16.04 LTS + Azure IoT Edge runtime VM image from Azure marketplace as Edge device.

[arsing]

(For reference, the docker CLI does this. Not only does it allow the user to give a leading http:// or https://, it also allows the user to give a path component after the hostname and strips that too.)

[github-actions[bot]]

This issue is being marked as stale because it has been open for 30 days with no activity.