Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Running inside of a custom docker container completes instantly without deploying

Open
  • Is something wrong?
#154 4 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
azure, docker, github-actions, typescript
Domain
ci-cd, cloud, devops

Research direction

Start by reproducing the workflow with container: mcr.microsoft.com/azure-cli and azure/bicep-deploy@v2, then inspect the logged Docker command and the action's exit behavior. Determine why the deployment does not run in this container context and whether the action should fail or document the requirement; done means the behavior is corrected or clearly documented and covered by an appropriate test.

Written by the indexing model from the issue text.

Description

Area - Error Handling Needs-Repro-Info

Hi,

I came across one issue - I am using a custom image to save some time installing the tools necessary:
container: mcr.microsoft.com/azure-cli

I am running the following job:

- name: '🚀 Deploy Bicep'
        uses: azure/bicep-deploy@v2
        with: 
          type: deployment
          operation: create
          name: myDeployment
          location: 'swedencentral'
          scope: subscription
          subscription-id: ${{ vars.AZURE_SUBSCRIPTION_ID }}
          template-file: 'deploy.bicep'
          parameters-file: 'deploy.${{ env.ENVIRONMENT_NAME }}.bicepparam'

This job completes within 2 seconds, and doesn't create the deployment. From the log it seems to try to start a docker container. So I guess this requires some additional configuration to support docker in docker?

##[debug]Evaluating condition for step: '🚀 Deploy Bicep'
##[debug]Evaluating: success()
##[debug]Evaluating success:
##[debug]=> true
##[debug]Result: true
##[debug]Starting: 🚀 Deploy Bicep
##[debug]Loading inputs
##[debug]Evaluating: format('myDeployment')
##[debug]Evaluating format:
##[debug]..Evaluating String:
##[debug]..=> 'myDeployment'
##[debug]..Evaluating Index:
##[debug]....Evaluating Index:
##[debug]......Evaluating Index:
##[debug]........Evaluating github:
##[debug]........=> Object
##[debug]........Evaluating String:
##[debug]........=> 'event'
##[debug]......=> Object
##[debug]......Evaluating String:
##[debug]......=> 'inputs'
##[debug]....=> null
##[debug]..=> null
##[debug]..Evaluating Index:
##[debug]....Evaluating Index:
##[debug]......Evaluating Index:
##[debug]........Evaluating github:
##[debug]........=> Object
##[debug]........Evaluating String:
##[debug]........=> 'event'
##[debug]......=> Object
##[debug]......Evaluating String:
##[debug]......=> 'inputs'
##[debug]....=> null
##[debug]..=> null
##[debug]..Evaluating Index:
##[debug]....Evaluating github:
##[debug]....=> Object
##[debug]....Evaluating String:
##[debug]....=> 'run_id'
##[debug]..=> '1825621'
##[debug]=> 'myDeployment'
##[debug]Result: 'myDeployment'
##[debug]Evaluating: vars.AZURE_SUBSCRIPTION_ID
##[debug]Evaluating Index:
##[debug]..Evaluating vars:
##[debug]..=> Object
##[debug]..Evaluating String:
##[debug]..=> 'AZURE_SUBSCRIPTION_ID'
##[debug]=> 'c5b....'
##[debug]Result: 'c5b...'
##[debug]Evaluating: format('deploy.***0***.bicepparam', env.ENVIRONMENT_NAME)
##[debug]Evaluating format:
##[debug]..Evaluating String:
##[debug]..=> 'deploy.***0***.bicepparam'
##[debug]..Evaluating Index:
##[debug]....Evaluating env:
##[debug]....=> Object
##[debug]....Evaluating String:
##[debug]....=> 'ENVIRONMENT_NAME'
##[debug]..=> 'dev'
##[debug]=> 'deploy.dev.bicepparam'
##[debug]Result: 'deploy.dev.bicepparam'
##[debug]Loading env
Run azure/bicep-deploy@v2
/usr/local/bin/docker exec  bf1975ba1fb[6](https://git.selfhosteddomain.com/)2f sh -c "cat /etc/*release | grep ^ID"
##[debug]ID=azurelinux
##[debug]Running JavaScript Action with default external tool: node20
Action config: ***
  "type": "deployment",
  "name": "myDeployment",
  "location": "swedencentral",
  "templateFile": "/__w/deploy.bicep",
  "parametersFile": "/__w/deploy.dev.bicepparam",
  "parameters": ***,
  "tags": ***,
  "maskedOutputs": [],
  "environment": "azureCloud",
  "operation": "create",
  "scope": ***
    "type": "subscription",
    "subscriptionId": "c5b..."
  ***,
  "whatIf": ***
    "excludeChangeTypes": []
  ***
***
##[debug]Node Action run completed with exit code 0
##[debug]Finishing: 🚀 Deploy Bicep

Image

If the job isn't able to start a docker container, shouldn't it fail? And maybe provide some documentation around this topic?

Dominant language
TypeScript
Stars
66
Forks
20
Avg merge
18h 43m
Merged PRs (30d)
19

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Azure/bicep-deploy

All issues in Azure/bicep-deploy

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.