Archive: ngccli_linux.zip
inflating: ngc
extracting: ngc.md5
[root@xxx /]# echo “export PATH="$PATH:$(pwd)"” >> ~/.bash_profile && source ~/.bash_profile
[root@xxx /]# ngc config set
Enter API key [****************************************************************cWU4MDQ2YzZmbGM3YWZwdjZtNDNyMmZnYTU6MTExZGFiZjItNDFhMy00OTczLTljMTEtMWQ5ODJhMGE0MTY4
Enter CLI output format type [json]. Choices: [ascii, csv, json]: json
Enter org [rqtvygzvvbuc]. Choices: [‘evoshdo5ltlx’]: evoshdo5ltlx
Enter team [no-team]. Choices: [‘no-team’]: no-team
Enter ace [no-ace]. Choices: [‘no-ace’]: no-ace
[root@xxx /]# ngc registry resource download-version “nvidia/jarvis/jarvis_quickstart:1.2.1-beta”
{
“download_end”: “2021-07-20 15:41:10.080991”,
“download_start”: “2021-07-20 15:41:06.073153”,
“download_time”: “4s”,
“files_downloaded”: 28,
“local_path”: “/jjarvis_quickstart_v1.2.1-beta-1”,
“size_downloaded”: “261.8 KB”,
“status”: “Completed”,
“transfer_id”: “jarvis_quickstart_v1.2.1-beta”
}
[root@xxx /]#
[root@xxx /]# cd jarvis_quickstart_v1.2.1-beta
[root@xxx jarvis_quickstart_v1.2.1-beta]# bash jarvis_init.sh
Logging into NGC docker registry if necessary…
NGC API Key is invalid. Please check and try again.
Hi @antarab ,
Can you please validate if you still have the valid API key, or validate the following steps that to generate the API key, and let us know?
1. Log in to your enterprise account on the NGC website [http://ngc.nvidia.com.](http://ngc.nvidia.com/)
2. Click Setup from the side menu, then click API Key from the Setup page.
3. On the API Key page, click Generate API Key.
4. In response to the warning that your old API Key will become invalid, click CONTINUE to generate the key.
Your API key is displayed with examples of how to use it.
Hi @ AakankshaS
Antara and myself have tried generating new keys couple of times but same error is coming.
Is there direct way to check if key is valid or not ?
[root@xxx /]# md5sum -c ngc.md5
ngc: OK
[root@xxx /]# ngc config set
bash: ngc: command not found
[root@xxx/]# echo “export PATH="$PATH:$(pwd)"” >> ~/.bash_profile && source ~/.bash_profile
[root@xxx /]# ngc config set
Enter API key [***************************************************************** ***************MTY4]. Choices: [<VALID_APIKEY>, ‘no-apikey’]: << MY API KEY>>
Enter CLI output format type [json]. Choices: [ascii, csv, json]: json
Enter org [evoshdo5ltlx]. Choices: [‘evoshdo5ltlx’]: evoshdo5ltlx
Enter team [no-team]. Choices: [‘no-team’]: no-team
Enter ace [no-ace]. Choices: [‘no-ace’]: no-ace
[root@XXX /]# docker login nvcr.io
Authenticating with existing credentials…
WARNING! Your password will be stored unencrypted in /root/.docker/config.json.
Configure a credential helper to remove this warning. See docker login | Docker Documentation
Login Succeeded
[root@xxx /]# ^C
[root@xxx /]# ngc registry resource download-version “nvidia/jarvis/jarvis_quickstart:1.2.1-beta”
{
“download_end”: “2021-07-23 00:37:24.398698”,
“download_start”: “2021-07-23 00:37:19.387191”,
“download_time”: “5s”,
“files_downloaded”: 28,
“local_path”: “/jjarvis_quickstart_v1.2.1-beta-1”,
“size_downloaded”: “261.8 KB”,
“status”: “Completed”,
“transfer_id”: “jarvis_quickstart_v1.2.1-beta”
}
[root@xxx /]# cd jarvis_quickstart_v1.2.1-beta
[root@xxx jarvis_quickstart_v1.2.1-beta]# bash jarvis_init.sh
Logging into NGC docker registry if necessary…
NGC API Key is invalid. Please check and try again.
Do you have an NGC_API_KEY variable set in your environment that is possibly invalid? If yes, that takes precedence over the key pulled from the NGC configuration file. The command that is failing is echo $NGC_API_KEY | docker login -u '$oauthtoken' --password-stdin nvcr.io
where $NGC_API_KEY either comes from your environment or is loaded from the ngc configuration file.
we are having the same issue, and would appreciate assistance.
the docker login succeeds, and we had no environment variable set.
have tried setting the NGC_API_KEY env variable, and got the following:
NGC_API_KEY is a deprecated environment variable. Please use NGC_CLI_API_KEY instead.
so we set NGC_CLI_API_KEY instead (after unsetting the deprecated variable), and it got seemingly ignored, as it still asked us for a key input:
Enter API key [no-apikey]. Choices: [<VALID_APIKEY>, 'no-apikey']:
after entering our key, we are still getting the same error:
Invalid API key for NGC service location [https://api.ngc.nvidia.com]. Please try again.
the key which I am attempting to use has the permissions for both “Secrets Manager” and for the “NGC Catalog” (the only two available options to me), it has not expired yet, and I am the “Org Owner.”
the ngc cli version we are using is NGC CLI 3.4.1.
please inform me if there is any further information we may give that can assist in solving this issue.
Having the same issue with new generated API key and authorizing the key to access NGC catalog, public API endpoints, Private Registry and Secret Manager. Am I missing any additional steps? NGC CLI version 2.16.0