azure-container-registry

问题 The bounty expires tomorrow . Answers to this question are eligible for a +50 reputation bounty. Piotr wants to draw more attention to this question: To help me diagnose the issue or propose a solution I am stuck and maybe you can help me out. (Update: After investigation, I do know that it is not working because the wwwroot folder for the Azure function after build/release is empty. The main question is why) I am trying to publish Azure Function using Azure Container Registry (Linux) This

问题 I'm trying to deploy the docker container on Azure App Service from Azure DevOps services. I've pushed the docker image to Azure Container Registry. When I try to create the release definition, I could not able to find the service connection for Azure Container Registry. I have created the service connection for ACR but it's not showing up in the list in Azure DevOps portal. When I selected 'Azure Container Repository' as the source type, the service connection is not visible in the drop down

问题 When pushing containers into a private Azure Container Registry using Docker Compose the Azure DevOps pipeline returns the following error: Pushing [container] ([registry]/[app]:latest)... The push refers to repository [docker.io/[registry]/[container]] denied: requested access to the resource is denied The azure-pipeline.yml file is taken from the Docker Compose example shown in the Microsoft Microservices eShopOnContainer example, here: variables: azureContainerRegistry: myregistry

问题 I have created a Azure Container Registry, and uploaded a custom ACI to the registry - no problem - everything works as intended. I have tried creating an container instance from the image using the Azure Portal, and no problems there either - however - when I want to automate things using C# with the Microsoft Azure Management Container Instance Fluent API, I run into problems, and even though I feel like I have been all over the Internet and the settings, looking for hidden obstructions, I

问题 Does anyone have any advice on how to pull from Azure container registry whilst running within Azure container service (kubernetes) I've tried a sample deployment like the following but the image pull is failing: kind: Deployment apiVersion: extensions/v1beta1 metadata: name: jenkins-master spec: replicas: 1 template: metadata: name: jenkins-master labels: name: jenkins-master spec: containers: - name: jenkins-master image: myregistry.azurecr.io/infrastructure/jenkins-master:1.0.0

问题 I am managing K8s cluster with AKS. My main aim to keep all the resources which are required for K8s in the same Vnet. One of the resources is ACR. I want to make it private and also it should be only able to access within the Vnet. Please let me know if its possible or point me in the right direction. Thanks! 回答1: Unfortunately, the ACR is just a repository to create and maintain Azure container registries to store and manage your private Docker container images. It seems that there is no

问题 I have a Container with a very simple Web App uploaded to an Azure Container Registry. I have an AKS cluster created. Now I want to deploy my container into AKS. I've found a number of tutorials on this, but they all seem to refer to YAML files that have very little, or no, explanation. I, therefore, have two questions: Is it necessary to use a YAML file to achieve this (kubectl create -f myyaml.yml)? (If not, what are the alternatives) Is there any documentation for exactly what needs to be

问题 Is there a way to delete specific tags only? I only found a way to delete the whole registry using the REST/cli-acr Thanks 回答1: We are hardening up the registry for our GA release later this month. We've deferred all new features while we focus on performance, reliability and additional azure data centers, delivering ACR across all public data centers by GA. We will provide deleting of images and tags in a future release. We're started to use https://github.com/Azure/acr/ to track features

问题 I have an IOTEdge device (Rapi3) and IotEdgeHub and IotEdgeagent are deployed and running. I have successfully built and deployed images (custom-vision example) to ACR and have configured Access Keys in the portal. I've added the respective credentials to my .env file. The deployment.json has been deployed using Create deployment for single device . Within IotAgent logs I can see a series of 500 errors: Executing command for operation ["create"] failed. Microsoft.Azure.Devices.Edge.Agent

问题 I'm deploying to azure container instances from the azure container registry (azure cli and/or portal). Azure blobfuse (on ubuntu 18) is giving me the following error: device not found, try 'modprobe fuse' first. The solution to this would be to use the --cap-add=SYS_ADMIN --device /dev/fuse flags when starting the container (docker run): can't open fuse device in a docker container when mounting a davfs2 volume However, the --cap-add flag is not supported by ACI: https://social.msdn