Azure / Azure/azure-quickstart-templates

Problems with Dokku deployment

Open
#3,716 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Bicep
Stars
14.9k
Forks
16.2k
Avg merge
6d 21h
Merged PRs (30d)
6

Description

[Deploy a Dokku Instance](https://github.com/Azure/azure-quickstart-templates/tree/master/dokku-vm)

### Issue Details
I have a problem with deploying this template on Asure. I've contacted MS support and they claim that the issue is with the json script:

> "extensions": [
>
> {
>
> "name": "initdokku",
>
> "type": "Microsoft.Azure.Extensions.CustomScript",
>
> "typeHandlerVersion": "2.0.3",
>
> "statuses": [
>
> {
>
> "code": "ProvisioningState/failed/0",
>
> "level": "Error",
>
> "displayStatus": "Provisioning failed",
>
> "message": "Enable failed: failed to execute command: command terminated with exit status=100"
>
> }
>
> ]
>
> }
>
> This is the Json being deployed, Line 215 they invoke CustomScript to run a script deploy_dokku.sh during VM creation:
>
> https://github.com/Azure/azure-quickstart-templates/blob/master/dokku-vm/azuredeploy.json#L215
>
> which is where that error above comes from.

### Repro steps (*if necessary, delete otherwise*)
1. I tried several regions (USWest, West Europe) and got the same error everythere during the deployment

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with dokku-vm/azuredeploy.json at line 215 and inspect how the CustomScript extension invokes deploy_dokku.sh during VM creation. Reproduce the Dokku deployment in a region such as USWest or West Europe and investigate the reported exit status 100. Done means the template provisions successfully without the CustomScript extension failure.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure, shell
Domain
cloud, devops, infrastructure
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.