container
9 items tagged with "container"
Articles
Error: database static dir ... does not match our static dir ... database configuration mismatch
Deploy Azure Function App with .NET 8 to Azure Container Apps via Bicep
Azure Function App can now be deployed into Azure Container Apps managed environment. This code snippet shows you how to deploy an Azure Function App created with .NET 8 (dotnet-isolated as runtime) into a managed environment of Azure Container Apps. The container source image is from GitHub (ghcr.io). You can also use any other container registry. Resources created This Bicep template creates the following resources: Blob Storage account Azure Log Analytics workspace Azure Application Insights Azure Container Apps managed environment Azure Function App Required credential You need to provide a container registry user name and password if you are using private registry. This template uses GitHub Packages.
Retrieve Client IP Address in Azure Container Apps with HTTP Ingress
Use Bicep to deploy Azure Container Apps with a free managed certificate
Context A few weeks ago when I was migrating Kontext from Azure App Services to Azure Container Apps, there was no free managed certificate. To address that issue, I used Let's Encrypt to create a certificate for Kontext. This process will take me a few minutes every few months . Now good news is that free managed certificate is also in preview in Azure Container Apps. The following code snippet shows you how to do that in Bicep. Note: \* when I deploy using Bicep, my container app was already existing. This means the domain verification is already added to my Azure DNS zones. If you are building a new app using managed certificate, I would suggest you do it in two steps: Bicep code to create container app enivronment, container and DNS records (incl. A record that points to IP of your container app and/or asuid verification TXT record). And then update Bicep code to add managed certificate and custom domains. In custom domains, you can reference the managed certificate ID directly. And then deploy Bicep code again with delta changes. \* The container image is from GitHub (not Azure Container Registry) in the following example. Issues When I run the deployments, Azure throws out one interim error like the following (however the deployment itself was not failing): The client 'XXX' with object id 'XXX' does not have authorization to perform action 'Microsoft.App/locations/managedCertificateOperationStatuses/read' over scope '/subscriptions/XXX/providers/Microsoft.App/locations/Australia East/managedCertificateOperationStatuses/XXX' or the scope is invalid. If access was recently granted, please refresh your credentials. (Code: AuthorizationFailed) After I wait for about 10 minutes the deployment becomes successful as the following screenshot does: !2023061092538-image.png References Custom domain names and bring your own certificates in Azure Container Apps Microsoft.App managedEnvironments/managedCertificates 2022-11-01-preview
Build Latest Hadoop on Windows 10 natively via Docker
Docker: no matching manifest for linux/amd64 in the manifest list entries
Diagrams
Forwarded Headers for ASP.NET Core Apps on Azure Container Apps
This diagram shows a scenario that ASP.NET Core application is hosted in Azure Container Apps and listens on HTTP port 8080 while Azure Container Apps ingress is configured with HTTPS. The original request protocol HTTPS is lost but the forward header X-Forwarded-Proto has value HTTPS that can be used by ASP.NET Core applications to generate the right URL with HTTPS protocol.
Mount Azure Storage Volumes to Container Group
Azure Files can be mounted to container groups in Azure Container Instances or App Services. To avoid latency, it is good practice to place the application containers in the same region as file storage.
Azure Kubernetes Service Components
This diagram shows you the key components and concepts in a Azure Kubernetes Service (AKS) cluster. In AKS, nodes (virtual machines) of same configuration are groups into pools. A node is a virtual machine in the cluster. A deployment represents identical pods. It defines the number of pods replica to deploy. A pod represents a single instance of your application. Usually one pod has one container though one pod can have multiple containers.