I created Container Registry, Web App for Containers and published image from Visual Studio but I don't see any image on the list? Why?
For your issue, I see that there is a refreshed symbol in the screenshot you provided. When you select the Registry server, there will be a process to read the registry and the process will cost a little time. So you need to wait a while.
And on my site, the Azure Container Registry works fine for the Web App for Container, you can see it here:
If any more question, you can give me the message.
Related
I configured Visual Studio to publish a docker image to Azure Container Registry and deploy it to an Azure App Service, the idea is: Every time I update my application, I'll publish the image to ACR and then, restart the App Service to update.
The problem is: the App Service container never updates, even the "latest" image doesn't look to update on ACR, the field "Tag last updated date" keeps the same, no matter how many times I publish the image from VS.
Actually, the only thing that modifies on ACR is the Pull Graphic count.
Any help?
Visual Studio only pushes the image if there is no other with the same tag on ACR.
I currently have a Linux app service (Web app) running a docker container, the containers are pushed to the ACR on build, with tags currently being the commit hash (shortened to the first 6 characters).
Continuous deployment has not been setup currently for various reasons.
In the "Container settings" window of the portal I've noticed that a large number of tags are missing - preventing the selection of some the latest built images.
All of the tags are currently available in the registry, however it seems that only ~100 tags are available in the drop down of the portal - which are listed in a alpha-numeric sorted list.
The web app is running without issue, however the tags are missing which is making selecting and deploying the containers directly from the portal an issue.
It appears that the Azure function which is returning the list of tags is causing the issue, as mentioned above only returning a partial number of the actual available tags.
I have no experience with more than a hundred images stored in the ACR. But as far as I know, there no limitation about the tags of the ACR images. You can see the Image Limits here. Also the App Service Limits.
I have pushed a working docker image to Azure Container Registry. I followed this tutorial to deploy it as a web application.
I followed the steps and it created a new web application, but it does not contain any files other than default Azure html that says Your App Service app is up and running. I am trying to figure out what went wrong. I checked the Activity logs and it says nothing. I checked the debug console <my-site>.scm.azurewebsites.net, and it does not contain any of the Docker Image files. How can I check what went wrong during the deployment?
Here is what I did.
I created a docker image, let's just call it my-image.
I checked it is working fine on my local machine.
I created a new tag to push the image to acr, docker tag <my-image_id> my-acr-username.azurecr.io/my-image.
Then I pushed it to acr, docker push my-acr-username.azurecr.io/my-image
I checked the acr repository to verify if it is pushed successfully.
Then I followed the above mentioned tutorial to deploy the image.
P.S. I am using Windows Containers.
I was using Windows Containers, and it turns out that Azure does not have a support for it yet. Unfortunately, it does not give you any errors or warnings if you try to deploy Windows Container. It simply doesn't work, and the user wonders what went wrong...
Here is my issue on their deployment engine Kudu.
I have followed the tutorials for building a .net core web application into a docker image, publishing to an azure container registry, and then I have setup my VSTS Release template to deploy the container to the app service.
This all appears to work, I can view my image in the container registry, and the deployment appears to succeed - but when navigating to the app service site, all I get is an HTTP 503 - Service unavailable.
The app service is started, I can see deployments in my file system via bash - so I wondered if I am missing something?
I do not have a 'startup' command in any of my templates, I wondered if it could be this?
The site works perfectly from VS2017, including debugging via docker, so it really is just a case of... how do I get the App Service to actually load and execute the image?
Thank you!
EDIT
Further to this, I have got access to the docker diagnostics logs which claim "image operating system "windows" cannot be used on this platform".
My base image is the microsoft/aspnetcore:2.0 image, which runs perfectly fine on my linux container in my development environment... but appears to not work in the Linux App Service?
Is the aspnetcore:2.0 base image not suitable for a linux app service?
I ended up resolving this week, hopefully the answer will help others.
When using VSTS Hosted build agents to produce images running off the docker base microsoft/aspnetcore:latest - unless you use the (Linux Preview) hosted build agent, you will get produced a windows container, which will not run on the linux app services.
Once I switched to using the hosted linux build agent, the container successfully loads, and my issue is resolved.
Another solution for the same error message:
Try microsoft/aspnetcore (without the tag/version :2.0) as image. If that doesn't work, check the docker logs as mentioned above and look for a solution based on the exact error (usually a missing dependency).
I've enabled Diagnostics in one of my Worker roles and published it to Azure. There was a new blob container created called "vsdiagnostics" and contained within in are two binary files. I'm assuming that these files contain the output of my Trace statements, but I'm unable to open these files as I have no idea what format they are in.
I've not found anything on www.windowsazure.com about it and most of the tools they recommend are very outdated. I have installed Cerebrata's Azure Diagnostics Manager, but that isn't able to load the Trace Logs.
If anyone could point me in the right direction I'd be grateful!
Most of the time when Visual Studio is used directly with your Windows Azure application, either with deployment or with troubleshooting, it creates a container in your Azure Storage and use this container to get/put data to in between your Azure instance and your Visual Studio instance. Mostly when you see container name start with VS* i.e. VSdeploy or VSDiagnostics, you can take an account that it is related with Visual Studio.
VSdeloy container is used when you deploy your application directly from Visual Studio. First your cspkg is transferred from desktop to this container and then to RDFE.
VSDiagnostics container is used to get the intellitrace data from your Azure Instance to your Visual Studio instance and when blog is downloaded to your desktop and then it is visible in VS as intellitrace logs.
When you opt to view Intellitrace logs, it appears that they are loaded into the vsdiagnostics blob, before being transferred to Visual Studio.