When I'm opening a Cloud Shell from my Azure subscription (xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx), then I get an error which says:
MOTD: To edit files in the shell, type: code, vim, emacs, vi or nano
VERBOSE: Authenticating to Azure ...
Out-File: /opt/microsoft/powershell/7/profile.ps1:143
Line |
143 | $addAzAccountParameters.Keys > $azErrorPath
| ~~~~~~~~~~~
| Read-only file system
VERBOSE: Building your Azure drive ...
What can I do to get a working Cloud Sheell to upload *.json files like templates and parameters from the $home directory.
⚠Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
@spidercloud Thanks for the feedback. We are actively investigating and will get back to you soon.
Hi,
I have the same problem can anybody please help?
VERBOSE: Authenticating to Azure ...
Out-File: /opt/microsoft/powershell/7/profile.ps1:143
Line |
143 | $addAzAccountParameters.Keys > $azErrorPath
| ~~~~~~~~~~~
| Read-only file system
VERBOSE: Building your Azure drive ...
Ok, I fix the issue on following way.
Open your local PowerShell (on your comp) as Administrator an type
Login-AzAccount
Log to your Azure account.
After that launch Azure and try Cloud shell.
Now it is fine for me, and I have uploaded 2 yml files successfully.
@Vladeexx Apologies for delayed response, great to hear your issue is resolved. Thanks for sharing the resolution for broader community here.
At this point it appears that there's no edits or updates needed to the documentation. We will go ahead and close this issue, however if you have any further queries please tag us in your reply and will be happy to reopen the thread and continue the conversation. Thank you
Hello
I have the same problem too. I have done what Vladeex says but the error stays the same. So I cannot upload templates nor run cmdlets
Cloud Shell has been working fine all these days but starting Lab 04 of AZ-104, TAsk 2 and opening Cloud Shell I got the error. I would like to fix it or I will not be able to deliver the course.
This afternoon I have opened Cloud Shell and it works!!! I have not done anything after this morning. Very strange behaviour
Hi all,
Rule no 1. Restart your system.
Cheers
On Sun, 26 Apr. 2020, 20:16 Franlusan, notifications@github.com wrote:
This afternoon I have opened Cloud Shell and it works!!! I have not done
anything after this morning. Very strange behaviour—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/azure-docs/issues/52462#issuecomment-619599041,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AL7OVNXONNBWWJZL2KVMSNDROR3AVANCNFSM4MIUZKLA
.
I got the same error and unable to use cloud shell .
MOTD: Switch to PowerShell from Bash: pwsh
VERBOSE: Authenticating to Azure ...
Out-File: /opt/microsoft/powershell/7/profile.ps1:143
Line |
143 | $addAzAccountParameters.Keys > $azErrorPath
| ~~~~~~~~~~~
| Read-only file system
VERBOSE: Building your Azure drive ...
I got the same error and unable to use cloud shell .
MOTD: Switch to PowerShell from Bash: pwsh
VERBOSE: Authenticating to Azure ...
Out-File: /opt/microsoft/powershell/7/profile.ps1:143
Line |
143 | $addAzAccountParameters.Keys > $azErrorPath
|~~~~~~~~~~~
| Read-only file system
VERBOSE: Building your Azure drive ...
Issue is fixed by recreating the cloud shell on another region .
Running into the same problem again today. I cannot even create the cloud drive in another region. It errors out.
I ran into same issue today.
$addAzAccountParameters.Keys > $azErrorPath
| ~~~~~~~~~~~
| Read-only file system
it was resolved after I removed that specific RG and created a new RG and SA
Same error, tried removing all resources (trial account) and recreating at different regions same error!
143 | $addAzAccountParameters.Keys > $azErrorPath
| ~~~~~~~~~~~
| Read-only file system
VERBOSE: Building your Azure drive ...
I had the same issue using bash (powershell has no issues). I tried recreating the storage, it wasnt helpful.
Did the old school hack..signed out, signed in to the portal...opened the cloud shell and clicked on the restart.
Magic happened, its working. Perhaps it might help you...give a try , No harm :)
Hi!
I had the same Issue but it's working after restart. Now, I've a question for Microsoft: