Intel® DevCloud
Help for those needing help starting or connecting to the Intel® DevCloud
1796 Discussions

Login error with devcloud

Mayank_K
Beginner
696 Views

I am trying to access the scheduled batch service of the instance Intel® Max Series GPU (PVC) on 4th Gen Intel® Xeon® processors - 1100 series (4x) as part of an Intel oneAPI center of excellence project. Following the method detailed in

github/bjodom/idc

Although I have precisely followed the steps I am getting the following error as I try to access the instance

mayank@DLSCD0055:~$ ssh u106717@idcbetabatch.eglb.intel.com
u106717@idcbetabatch.eglb.intel.com: Permission denied (publickey).

 

I am using WSL2 and the config file contents are as below.

Host myidc 
Hostname idcbetabatch.eglb.intel.com
User u106717 
IdentityFile ~/.ssh/id_ed25519_idc
#ProxyCommand /usr/bin/nc -x YourProxy:XXXX %h %p # Uncomment if necessary
ServerAliveInterval 60
ServerAliveCountMax 10
StrictHostKeyChecking no 
UserKnownHostsFile=/dev/null

 

Kindly help me resolve the issue.

 

Regards,

Mayank

0 Kudos
3 Replies
Megat_Intel
Moderator
662 Views

Hi Mayank,

Thank you for reaching out to Intel® Communities.

 

For your information, the public key must be saved in the profile before starting an instance. The instance will need to be relaunched if the public key is updated after an instance is launched.

 

On the other hand, are you using any proxy for your internet connection? If not, please modify the config file (~/.ssh/config) as below and initiate the ssh again in a new terminal.

 

Host myidc
Hostname idcbetabatch.eglb.intel.com
User u106717
IdentityFile ~/.ssh/id_ed25519_idc
ServerAliveInterval 60
ServerAliveCountMax 10
StrictHostKeyChecking no
UserKnownHostsFile=/dev/null

 

 

 

Regards,

Megat

 

0 Kudos
Mayank_K
Beginner
655 Views

Hi Megat,

 

The issue is resolved and I am now able to access the Intel Devcloud. Thank you

 

Kind regards,

Mayank

0 Kudos
Megat_Intel
Moderator
654 Views

Hi Mayank,

We're glad you are able to access the instance. This thread will no longer be monitored since this issue has been resolved. If you need any additional information from Intel, please submit a new question.

 

 

Regards,

Megat


0 Kudos
Reply