Deployment hangs indefinitely on azure-cli Docker

At this time, I have tried using multiple image versions:
- 2.63.0 (the last Alpine build)
- 2.67.0 (the latest build available for `deployment_script` resources)

In both cases, I get inconsistent hanging behaviors.

For 2.63.0, where I can `apk add npm` to install the CLI, I can reach the point of deploying but am left in an indefinite hanging from the Azure Portal.


Excerpt from logs with `--verbose=silly`:


This seems consistent with the `--app-location .` issue, but I'm using an unzipped archive in the `./dist/` directory.


The odd thing about this scenario is that I can run this locally, and it works. By that, I mean I can pull the same container, down to the SHA256 version, run the same script with the same environment variables, and it works. I have no idea why it's problematic in ACR via the Deploy Script.



For 2.67.0, I have to install npm via `tdnf` first. This seems to never hit the instance. When running with `--verbose=silly`, it exits without indicating what went wrong. This is repeatable locally.


If I execute without `--verbose=silly`, I get stuck during the deployment indefinitely. The portal never updates from this state. It's just hanging.


Using 2.0.4 in both cases:

2.63.0:

2.67.0:

My deployment is a simple `index.html` at the moment, but will eventually be a react SPA.


**Describe the bug**
Cannot deploy using `azure-cli:2.63.0` or `azure-cli:2.67.0` images in ACR via Azure Deployment Script

**To Reproduce**
See the screenshots above.

**Expected behavior**
On invoking the `deploy` command, I should be able to deploy.

**Desktop (please complete the following information):**

My host is Ubuntu 24.04, but all commands are being run via the listed containers.

**Additional context**
To my understanding, this is the only option I have for deployment. This deployment script is part of a Marketplace Managed Application that is being developed, and I need to be able to deploy code from private repositories without granting permanent access to end users. "Use GitHub Actions" or "Azure Devops Pipelines" are not valid responses.

Beginne damit, die deployment_script-Bereitstellung mit azure-cli:2.63.0 und 2.67.0 unter Verwendung des App-Speicherorts ./dist/ und --verbose=silly wie beschrieben zu reproduzieren. Verfolge, wo der deploy-Befehl stoppt, und vergleiche das Verhalten des lokalen Containers mit der Ausführung in Azure Container Registry; abgeschlossen bedeutet, dass die Bereitstellung abgeschlossen wird oder einen eindeutigen Fehler meldet, anstatt auf unbestimmte Zeit zu hängen.

Vom Indexierungsmodell aus dem Issue-Text verfasst.