This message was deleted.

Hi, I looked into it a bit last week.. It looks like a bug that needs to be addressed either on the Rancher Desktop or the upstream nerdctl side. I want to investigate this a bit more but couldn't spend much time due to my still broken environment.. Once I have my environment fixed, I am essentially planning to give this credential helper a try instead of

gcloud

based approach.. May be you can give it a try yourself and let us know if it works please?

K, I'll give it a try

Hi, I finally could fix my env and look into this.. Thanks for your patience.. Ok, there's a bug in the current Rancher Desktop 1.6.2 release in terms of supporting credential helpers with

nerdctl

. The issue has already been resolved in the work in progress version for the upcoming release this month. Btn, the

gcloud

approach still seems to be having problems.. Here are the steps that worked for me in the dev version.. • Download and copy the docker-credential-gcr to a folder on your PATH • Copy your credentials file to

%APPDATA%/gcloud/application_default_credentials.json

if Windows, or to

$HOME/.config/gcloud/application_default_credentials.json

on other OSs • Run

docker-credential-gcr config --token-source "env,store"

• Run

docker-credential-gcr configure-docker

• Try

pull

,

push

commands as usual. For example, ◦

nerdctl pull hello-world

◦

nerdctl tag hello-world <http://LOCATION-docker.pkg.dev/PROJECT-ID/REPOSITORY/hello-world:rdtest|LOCATION-docker.pkg.dev/PROJECT-ID/REPOSITORY/hello-world:rdtest>

◦

nerdctl push <http://LOCATION-docker.pkg.dev/PROJECT-ID/REPOSITORY/hello-world:rdtest|LOCATION-docker.pkg.dev/PROJECT-ID/REPOSITORY/hello-world:rdtest>

The issue has already been resolved in the work in progress version for the upcoming release this month.

How should I download/install this dev version?

Which OS are you on?

MacOS Monterey 12.5.1

You can download the latest CI build from the GitHub repo, for example the latest one as of today is here.. Please use with caution as this is a WIP version and we are in the process of fine tuning things for the release.

Copy your credentials file to

%APPDATA%/gcloud/application_default_credentials.json

In this step, which credentials file are you referring to?

It's the key file, which you can download from the GCP web console.. The content looks like this..

{
  "type": "xxxxxxxxxxxxxxxxxxxxxxxxxx",
  "project_id": "xxxxxxxxxxxxxxxxxxxxxxxxxx",
  "private_key_id": "xxxxxxxxxxxxxxxxxxxxxxxxxx",
  "private_key": "xxxxxxxxxxxxxxxxxxxxxxxxxx",
  "client_email": "xxxxxxxxxxxxxxxxxxxxxxxxxx",
  "client_id": "xxxxxxxxxxxxxxxxxxxxxxxxxx",
  "auth_uri": "xxxxxxxxxxxxxxxxxxxxxxxxxx",
  "token_uri": "xxxxxxxxxxxxxxxxxxxxxxxxxx",
  "auth_provider_x509_cert_url": "xxxxxxxxxxxxxxxxxxxxxxxxxx",
  "client_x509_cert_url": "xxxxxxxxxxxxxxxxxxxxxxxxxx"
}

I'm getting

erdctl pull docker.pkg.dev/activated-manage/ai/eve:base-v10
INFO[0000] trying next host                              error="failed to do request: Head \"<https://docker.pkg.dev/v2/activated-manage/ai/eve/manifests/base-v10>\": proxyconnect tcp: dial tcp 127.0.0.1:3128: connect: connection refused" host=docker.pkg.dev
ERRO[0000] server "docker.pkg.dev" does not seem to support HTTPS  error="failed to resolve reference \"docker.pkg.dev/activated-manage/ai/eve:base-v10\": failed to do request: Head \"<https://docker.pkg.dev/v2/activated-manage/ai/eve/manifests/base-v10>\": proxyconnect tcp: dial tcp 127.0.0.1:3128: connect: connection refused"
INFO[0000] Hint: you may want to try --insecure-registry to allow plain HTTP (if you are in a trusted network) 
FATA[0000] failed to resolve reference "docker.pkg.dev/activated-manage/ai/eve:base-v10": failed to do request: Head "<https://docker.pkg.dev/v2/activated-manage/ai/eve/manifests/base-v10>": proxyconnect tcp: dial tcp 127.0.0.1:3128: connect: connection refused 
Error: exit status 1

Can you please share your docker config.json.. From the error message, it looks like your setup still tries to use

gcloud

for credentials.

I've updated my credentials to be

{
  "auths": {},
  "credsStore": "desktop",
  "credHelpers": {
    "us-central1-docker.pkg.dev": "gcr"
  }
}

I am not sure, why the same setup would not work on macOS. Let me file a GitHub issue on our repo so that one of our team members using macOS can investigate this further.

Hey guys, any news about this? This is also preventing me from moving from Docker Desktop to Rancher Desktop.