Azure – Set Environment Variables on Azure App Service (Docker Instance)

azureazure-web-apps

When creating an App Service in Azure and selecting Docker Container as a type of App, where do you set Environment Variables?

My App is built in Azure by:
1. Create Resource > App Service > Publish > Choose Docker Image (rather than code)
2. Point to Docker container in Azure registry.

The app builds fine, but I wish to pass in environment variables during the docker run command (on other services you simply set environment variables). When the app builds, you can see in the logs the app service runs" docker run…." and passes in –env variables. Like so

"docker run -d -p 56996:80 –name nameofapp_7 -e WEBSITE_SITE_NAME=AngularApp"

What I need to know is where in the Azure Portal can you set the variables to be passed into the run command. i.e. WEBSITE_SITE_NAME ?

Best Answer

Any app settings you configure in the web application are passed into the container as environment variables. You can configure these in the portal, through CLI or ARM Template.

Related Solutions

Azure – Connecting to Blob storage from app service through vnet

This is an old issue.

For Azure Web App service VNET intergration,it gives your web app access to resources in your virtual network but does not grant private access to your web app from the virtual network. Private site access refers to making your app only accessible from a private network such as from within an Azure virtual network. Private site access is only available with an ASE configured with an Internal Load Balancer (ILB). For details on using an ILB ASE, start with the article here: Creating and using an ILB ASE.

It means that with VNET intergration, you web app can connect the VNET from outside, but the web app is not inside the VNET.

So, the firewall for the storage account is just allow the traffic from the VNET, cannot allow the traffic outside the VNET.

For you scenario, one method is using ILB ASE. It can makes your web app into a VNET.

Azure – Fixing Docker App Error ‘Site Did Not Start Within Expected Time Limit’

The container must implement an HTTP 404 (Not Found) error handler.

When Azure starts a container, the warmup request checks the server by requesting resources to ensure that it is responding. If one of the requested resources is not found and the container does not have an HTTP 404 (Not Found) error handler, then the request will timeout and the container will be stopped.

Docker Container Port Configuration

The Azure PORT flag is not needed. The WEBSITES_PORT flag should be set to whichever port is exposed within the container.

Set WEBSITES_PORT from the Azure CLI as follows:

az webapp config appsettings set --resource-group <resource-group-name> --name <app-name> --settings WEBSITES_PORT=8000

Or use the Azure portal:
Your app > Settings > Configuration > Application settings

Flask Example - HTTP 404 Error Handler

from flask import Flask
from werkzeug.exceptions import Forbidden, HTTPException, NotFound, RequestTimeout, Unauthorized


app = Flask(__name__)


@app.route('/')
def hello():
    return "Hello Flask!"


@app.errorhandler(NotFound)
def page_not_found_handler(e: HTTPException):
    return render_template('404.html'), 404


@app.errorhandler(Unauthorized)
def unauthorized_handler(e: HTTPException):
    return render_template('401.html'), 401


@app.errorhandler(Forbidden)
def forbidden_handler(e: HTTPException):
    return render_template('403.html'), 403


@app.errorhandler(RequestTimeout)
def request_timeout_handler(e: HTTPException):
    return render_template('408.html'), 408


if __name__ == '__main__':
    app.run()