Azure Storage Accounts
Globally unique resources that provide access to data management services and serve as the parent namespace for the services.
3,436 questions
Shell script won't upload to storage blob?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(0, 31%, 10%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
AndrewW
0
Reputation points
So, for use with an image customisation process I'm doing, I thought I'd upload a sample bash script to a storage account, so I can reference it during the image build process.
But, unhelpfully, all I was getting was:
Failed to upload blob(s)
Failed to upload 1 out of 1 blob(s): script.sh: error
Similarly vague errors in Storage Explorer about my SAS key. The script was just a simple placeholder to test it was being called:
#!/bin/bash
echo bashy-bash > /tmp/bashaw.txt
However, it just won't upload. I discovered if I remove that first line, it uploads fine. If I remove just the "!" character, it works fine.
OK, so it's some sort of prohibited-content then (thanks for the help error message, MS), but I can't find any explanation as to why it's not allowed anywhere.
Anyone got any suggestions please?
Thanks
{count} votes
-
Sumarigo-MSFT 47,516 Reputation points Microsoft Employee2024-01-10T14:01:09.0433333+00:00 @AndrewW Thank you for posting your query here,
Can you share the screenshot of the error message?
Is this happening for the particular Storage account(blob)?It could be intermittently issue, can you refresh the page ( Try to logout and login back)
It's possible that the issue you are experiencing is related to the content type of the file you are trying to upload. By default, Azure Storage blocks certain file types that are considered potentially harmful, such as executable files and scripts.
In your case, the first line of your script (
#!/bin/bash) is a shebang line that specifies the interpreter to use for the script. This may be triggering Azure Storage to block the file due to its content type.To resolve this issue, you can try changing the content type of the file to something that is not blocked by Azure Storage. For example, you can change the content type to
text/plainorapplication/octet-stream.However I would like to work closer on this issue
-
AndrewW 0 Reputation points
2024-01-11T10:45:41.34+00:00 Thanks @Sumarigo-MSFT , as you can see it's not the most helpful of error messages.
Also, I see no option to change the content type during upload.
-
AndrewW 0 Reputation points
2024-01-11T10:49:07.0133333+00:00 Not sure where my reply went to... :(
No option to change content type in portal?
-
AndrewW 0 Reputation points
2024-01-11T10:51:05.0233333+00:00 Can you provide a link that explains prohibited file types and content please?
It makes it difficult to use storage accounts for scripts to be used during VM deployment if "#!" is considered illegal. Why would MS block such a thing?
-
Sumarigo-MSFT 47,516 Reputation points Microsoft Employee
2024-01-24T06:31:34.8166667+00:00 @AndrewW I wish to engage with you offline for a closer look and provide a quick and specialized assistance, please send an email with subject line “Attn:subm” to AzCommunity[at]Microsoft[dot]com referencing this thread and the Azure subscription ID, I will follow-up with you. Once again, apologies for any inconvenience with this issue.
Thanks for your patience and co-operation. -
AndrewW 0 Reputation points
2024-01-29T09:44:03.8+00:00 Hi @Sumarigo-MSFT , I emailed you early last week, hope you received.
Sign in to comment
Sign in to answer