Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

compose: container app not deployed after azd adding a database and provisioning changes for first time #4733

Open
JeffreyCA opened this issue Jan 28, 2025 · 0 comments
Labels
compose composability

Comments

@JeffreyCA
Copy link
Contributor

JeffreyCA commented Jan 28, 2025

Repro steps

  1. azd config set alpha.compose on
  2. In an empty directory: azd init -t JeffreyCA/minimal-flask-app (source) and provide an environment name.
  3. azd add - Select Database, then input the following:
    • Which type of database? MongoDB
    • Input the name of the app database (MongoDB): mdb
    • Select the service(s) that uses this resource: [✓] pyservice
    • Accept changes to azure.yaml? Yes
    • Do you want to provision these changes? Yes
  4. Proceed through remaining prompts to provision the changes

The Python Flask app fails to load at the container app endpoint, and the container app revision reports a status of: "The TargetPort 5000 does not match the listening port 80".

Image

Another way to repro the issue is to clone the above sample app with an empty azure.yml, then progressively azd add a container app (do not provision) and then a database (provision).

One workaround is to run azd up afterwards to deploy the changes.

@JeffreyCA JeffreyCA added the compose composability label Jan 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
compose composability
Projects
None yet
Development

No branches or pull requests

1 participant