This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(227.2, 7.000000000000001%, 32%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJH%3C/text%3E%3C/svg%3E)
Hm. I am having additional issues related to "Missing environment variables." I am assuming that maybe somewhere it is because I need to add these variables inside both the build and the run phase inside my Dockerfile, given that I cannot find a slot to update this inside the Azure DevOps portal.
@RyanHill
I don't seem to find a spot to add these within Azure DevOps. I tried to update my Dockerfile and re-run docker build and docker push, then "Run Pipeline" in Azure DevOps, but still get same error message as before where I am missing environment variables.
This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Hey @James Hizon
Thanks for meeting with me offline to see your exact issue. We were able to resolve your issue by splitting your buildAndPush task into two separate steps per this troubleshooting step that referenced this stackoverflow post.
Once we got your arguments added, you were able to successfully run your yaml pipeline.
Ok, this is good. Thank you.
So, I think this Azure Pipeline step was to build and push to ACR (I assume that we wouldn't use Docker or Azure Pipelines for Azure App Service or Azure Container Apps?).
The next step would then be to set up the web app in Azure App Services and then here we can also point to our custom domain? This would be what I would want to do next.
From what I recall, I am at this step but then again we had to deal with that issue with the Azure DevOps portal:
Perhaps, let's have maybe one last call to confirm this is all up and running properly such that Azure App Service is properly in sync with Azure DevOps / Azure Pipelines.
I was able to get the custom domain setup, as a plus:
Hey @James Hizon no, you don't want to this setting. Since you're using your Azure DevOps pipeline to build your docker image and push it to your container registry, you want to leave the setting set as Container Registry.
You would change this if you elected to push the code directly to the app service as opposed of using a docker image. Kudos to you for getting the custom domain configured!
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(16, 60%, 11%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESC%3C/text%3E%3C/svg%3E)
Hi @James Hizon ,
I have seen the previous question conversation and providing the below response to help with the issue of missing environment variables.
One thing you can try is passing the environment variables when defining the pipeline YAML, you can include the variables and check they are passed as build arguments to Docker. This way, when the image is built, it already has the required variables embedded. In your azure-pipelines.yml
variables:
DATABASE_URL: $(DATABASE_URL)
API_KEY: $(API_KEY)
steps:
- task: Docker@2
inputs:
command: 'buildAndPush'
repository: '<your-acr-name>.azurecr.io/<your-image-name>'
dockerfile: '**/Dockerfile'
containerRegistry: '<your-acr-service-connection>'
tags: 'latest'
arguments: '--build-arg DATABASE_URL=$(DATABASE_URL) --build-arg API_KEY=$(API_KEY)'
If you haven't already, make sure that DATABASE_URL and API_KEY are actually defined in Azure DevOps under the pipeline variables section. You can find this by going into your pipeline in Azure DevOps, clicking "Edit," navigating to the "Variables" tab, and adding them there.
Add variables.
Theres is another approach using a .env file. Instead of manually passing variables in the pipeline, the build process can pull them from a file. You can generate this file dynamically in the pipeline.
- script: echo "DATABASE_URL=$(DATABASE_URL)\nAPI_KEY=$(API_KEY)" > .env
displayName: 'Create .env file'
- task: Docker@2
inputs:
command: 'buildAndPush'
repository: '<your-acr-name>.azurecr.io/<your-image-name>'
dockerfile: '**/Dockerfile'
containerRegistry: '<your-acr-service-connection>'
tags: 'latest'
arguments: '--env-file .env'
If you want to modify the Dockerfile to handle this use ARG for build-time variables and ENV for runtime variables.
ARG DATABASE_URL
ARG API_KEY
ENV DATABASE_URL=$DATABASE_URL
ENV API_KEY=$API_KEY
RUN echo "Database URL: $DATABASE_URL"
RUN echo "API Key: $API_KEY"
Hope it helps!
Please do not forget to click "Accept the answer” and Yes wherever the information provided helps you, this can be beneficial to other community members.
If you have any other questions or still running into more issues, let me know in the "comments" and I would be happy to help you.