Business
Jobs
  • About Us
  • Solutions
    • Job Postings
      Post your job and receive qualified candidates in 48h.
    • Candidate Assessments
      500+ technical and psychological tests, plus anti-fraud.
    • Headhunting
      Tailor-made executive search from start to finish.
    • Payroll + EOR
      Payroll dispersal and EOR across 15+ LATAM countries.
  • Pricing
  • Jobs

0

205
Views
Azure Function Runtime Unreachable when deploying from Azure devops pipeline

Thanks for taking the time to read. My current setup is as follows:

I have an azure function service up and running, an az function project in visual studio (which I have tested and it runs without issue), a build pipeline in azure devops that deploys a docker image with my function project to an azure container registry.

My problem:

When I try to setup my function service for CI/CD from my devops pipeline, I get the following error on the "functions" tab on my app: "Azure Functions runtime is unreachable". Also none of the functions from my code are listed. In the deployment center however, I get a message "Deployed successfully to production", and it shows my built docker container image name.

Troubleshooting:

In the deployment center of my function app (in the az portal), I set my app to read directly from the azure container registry (using the exact same docker image that my pipeline built earlier), and that worked perfectly - deployment successful and I could see my individual functions name. When I switched back to CI/CD deployment however I got the same problem as earlier.

Trying to see if anyone has had the same problem or could suggest a path forward for getting CI/CD integration working.

I pasted my yaml file below with some names changed for privacy.

trigger:
- master

pool:
  vmImage: 'ubuntu-latest'

variables:
  project: 'myProjectName'
  environment: 'prod'
  dockerfile: '**/Dockerfile'
  azureResource: 'myScraperFunction'
  imageName: myScraperFunction

steps:
- task: Docker@2
  displayName: Build
  inputs:
    command: build
    containerRegistry: $(azureContainerRegistryName)
    repository: '$(Build.Repository.Name)-$(project)'
    tags: '$(Build.BuildNumber)-$(environment)'
    Dockerfile: $(dockerfile)
    buildContext: '$(Build.SourcesDirectory)'
    arguments: --build-arg PAT=$(System.AccessToken)

- task: Docker@2
  displayName: Push
  inputs:
    command: push
    containerRegistry: $(azureContainerRegistryName)
    repository: '$(Build.Repository.Name)-$(project)'
    tags: '$(Build.BuildNumber)-$(environment)'
    Dockerfile: $(dockerfile)       

- task: AzureFunctionAppContainer@1
  displayName: 'Azure Function App on Container Deploy: $(azureResource)'
  inputs:
    azureSubscription: '$(azureSubscription)'
    appName: $(azureResource)
    imageName: '$(azureContainerRegistry)/$(imageName):$(Build.BuildNumber)-$(environment)'
over 4 years ago · Santiago Trujillo
1 answers
Answer question

0

Configuration/typing issue in yml file. Repository name during build step was hard-coded (I didn't use a variable like what was posted above) and did not match repo name in deploy step because of a spelling error.

over 4 years ago · Santiago Trujillo Report
Answer question
Find remote jobs

Discover the new way to find a job!

Top jobs
Top job categories
Business
Post vacancy Pricing Sales
Legal
Terms and conditions Privacy policy
© 2026 PeakU Inc. All Rights Reserved.
Andres GPT
Show me some job opportunities
There's an error!