I can copy from production to development just fine, but when I try to copy from development to production I get this error:
404, resource not found.
For the command:
AzCopy /Dest:https://accountname.blob.core.windows.net/appimage /Source:http://127.0.0.1:10000/devstoreaccount1/appimage /DestKey:key /SourceType:blob /SourceKey:Eby8vdM02xNOcqFlqUwJPLlmEtlCDXJ1OUzFT50uSRZ6IFsuFq2UVErCz4I6tq/K1SZFPTOtr/KBHBeksoGMGw== /S
I have tried both storage emulator 5.0 and the latest 5.3 and different AZ copies. All my containers are public access.
This error just doesn't make any sense.
It is not supported to transfer from storage emulator to cloud directly. See this issue.
You can add /SyncCopy parameter to your command.
It automatically downloads blobs from emulator to local memory and then uploads them to cloud.
Related
I have an already existing docker image that is linux/arm64 because i have an m1 mac, but I want to host it on azure.
{"code":"DeploymentFailed","message":"At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/DeployOperations for usage details.","details":[{"code":"WebhookInvalidParameterValue","message":"The following field(s) are either invalid or missing. Invalid value: "myregistry.azurecr.io/myproject:latest": image OS/Arc must be linux/amd64 but found linux/arm64: template.containers.myproject.image."}]}
Is it a way to host the existing image on azure or convert it to linux/amd64?
Currently, Azure Container Apps only support Linux-based x86-64 (linux/amd64) container images so you can't deploy an ARM-based container. Documentation
On a M1 Mac, you can build multiarch containers using Buildx. This way, you can build an x86-64 version of your container that you'll be able to deploy on Container Apps. Documentation
You can also build the container image using your Azure Container Registry, instead of building it locally using cross-compile. ACR can build it for amd64.
https://learn.microsoft.com/en-us/cli/azure/acr?view=azure-cli-latest#az-acr-build
Need to install LibreOffice to my Azure App Service.
1. Azure DevOps
I used powershell Start-Process to silent install but getting Permission denied.
Start-Process: /home/vsts/work/_temp/5cc8c99d-ed13-4b1b-823b-3cd9b56fdd1b.ps1:5
Line |
5 | Start-Process /home/vsts/work/1/s\LibreOffice_7.4.0_Win_x64.msi -Argu …
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| An error occurred trying to start process
| '/home/vsts/work/1/s/LibreOffice_7.4.0_Win_x64.msi' with
| working directory '/home/vsts/work/1/s'. Permission denied
2. Kudu terminal
Getting Access Denied error when trying to run Start-Process manually.
Are there any alternatives to achieve this?
Not possible to install something on the host. The alternative is to use a docker container which has it already installed.
https://azure.github.io/AppService/windows-containers/
App Service supports Windows Containers! Deploying your application in a Windows Container enables you to bring along dependencies such as custom fonts, cultures and GAC deployed assemblies. When deploying a containerized application, the Windows Container is an isolation and security boundary. As a result, calls to libraries that would normally be blocked by the Azure App Service will instead succeed when running inside of a Windows Container.
I am unable to install the VSTS Agent Azure VM extension on an Azure VM. I tried both the Install extension blade in the Azure portal and the Powershell option. When I try from the portal it just gets stuck at transitioning. If I run the Powershell script it gets stuck trying to connect to server.
I was able to install it on another server without any issues. The 2 servers are part of a web farm so they are exact images.
I am following the steps detailed at this url https://learn.microsoft.com/en-us/vsts/build-release/concepts/definitions/release/deployment-groups/howto-provision-deployment-group-agents?view=vsts .
I am trying to deploy from VSTS to an Azure VM.
This is the screen when I try to run the powershell script.
Run the config file directly (from C:/vstsagent folder) in cmdline and try again with dev.azure.com/{organisation name} url.
We have .Net project build definition on VSTS and it's using Azure Storage Emulator for running tests. And we want to use Hosted 2017 agents for the build definition.
I saw this question (Azure SDK not available on Hosted VS2017 VSTS Build Agent) and the comment that I can use command "C:\Program Files (x86)\Microsoft SDKs\Azure\Storage Emulator\AzureStorageEmulator.exe init /server (localdb)\MSSQLLocalDb" to initialize Azure Storage Emulator.
However, when I tried to start Azure Storage Emulator with command "C:\Program Files (x86)\Microsoft SDKs\Azure\Storage Emulator\AzureStorageEmulator.exe start", it failed with Error: Unable to start the storage emulator.
Is there any way to start Azure Storage Emulator on VSTS Hosted 2017 agent?
Command and Error
It is now possible.
See the other answer:
https://stackoverflow.com/a/51726177/1830814
Some more info here:
https://developercommunity.visualstudio.com/content/problem/238481/hosted-visual-studio-2017-errorno-available-sql-in.html#
The VSTS Hosted agent is running as service that you can’t start storage emulator (init is ok).
A related thread: VSO Hosted Build Controller - Is the Azure Storage Emulator supported?
Update:
Based on the test, the Azure Storage Emulator can be started on Hosted VS2017 agent now.
I understand that we can mount Azure File shares onto Ubuntu Linux VM. Right now, is there any alternative to moving data into SUSE Linux VM instead of Ubuntu VMs?
moreover, my data lies on Blob containers instead of fileshare. if needed, i can move data into Fileshare from Blob containers. Any suggestions, please.
You could mount Azure File shares onto Suse Linux VM. You could use the following to mount your File shares.
sudo zypper install samba*
##create your directory
mkdir -p /home/test
sudo mount -t cifs
//shuitestdiag630.file.core.windows.net/shuifile [mount point] -o
vers=3.0,username=shuitestdiag630,password=[storage account access
key],dir_mode=0777,file_mode=0777
More information please refer to the article
Also, you could download your blob data to your VM. You could use Azure CLI to manage your blob data. Azure CLI supports to run on Linux and download blobs. More information about Azure CLI please refer to the article