You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have created a simple .NET Aspire application that only has Aspire integration (PostgreSQL) and no .NET project. The application runs successfully on a local machine. When running "azd up" I encounter the following error:
`PS C:\Users\mja\source\repos\Aspire-Empty-App-Bug> azd up
Packaging services (azd package)
Provisioning Azure resources (azd provision)
Provisioning Azure resources can take some time.
Subscription: Personal-MJA-Dev (dfe850c1-aba7-48eb-ac7a-7ffc85b7579b)
Location: North Europe
ERROR: error executing step command 'deploy --all': failed deploying service 'postgres': logging in to registry: could not determine container registry endpoint, ensure 'registry' has been set in the docker options or 'AZURE_CONTAINER_REGISTRY_ENDPOINT' environment variable has been set
PS C:\Users\mja\source\repos\Aspire-Empty-App-Bug>`
Expected Behavior
I want to run and deploy to Azure an Aspire application that consists only of integration (no custom .NET project)
ERROR: error executing step command 'deploy --all': failed deploying service 'postgres': logging in to registry: could not determine container registry endpoint, ensure 'registry' has been set in the docker options or 'AZURE_CONTAINER_REGISTRY_ENDPOINT' environment variable has been set
@eerhardt had a nice catch here and figure this was actually an issue in AZD because the ACA definition provided by the AppHost contains a public image. AZD had a bug trying to log in to ACR before deploying.
Is there an existing issue for this?
Describe the bug
I have created a simple .NET Aspire application that only has Aspire integration (PostgreSQL) and no .NET project. The application runs successfully on a local machine. When running "azd up" I encounter the following error:
`PS C:\Users\mja\source\repos\Aspire-Empty-App-Bug> azd up
Packaging services (azd package)
Provisioning Azure resources (azd provision)
Provisioning Azure resources can take some time.
Subscription: Personal-MJA-Dev (dfe850c1-aba7-48eb-ac7a-7ffc85b7579b)
Location: North Europe
You can view detailed progress in the Azure Portal:
https://portal.azure.com/#view/HubsExtension/DeploymentDetailsBlade/~/overview/id/%2Fsubscriptions%2Fdfe850c1-aba7-48eb-ac7a-7ffc85b7579b%2Fproviders%2FMicrosoft.Resources%2Fdeployments%2Fazd-empty-aspire-app-demo-1743362595
(✓) Done: Resource group: rg-azd-empty-aspire-app-demo (659ms)
(✓) Done: Log Analytics workspace: law-vnkwbrq6pkw4q (797ms)
(✓) Done: Container Apps Environment: cae-vnkwbrq6pkw4q (2m22.922s)
Deploying services (azd deploy)
(x) Failed: Deploying service postgres
ERROR: error executing step command 'deploy --all': failed deploying service 'postgres': logging in to registry: could not determine container registry endpoint, ensure 'registry' has been set in the docker options or 'AZURE_CONTAINER_REGISTRY_ENDPOINT' environment variable has been set
PS C:\Users\mja\source\repos\Aspire-Empty-App-Bug>`
Expected Behavior
I want to run and deploy to Azure an Aspire application that consists only of integration (no custom .NET project)
Steps To Reproduce
Exceptions (if any)
Deploying services (azd deploy)
(x) Failed: Deploying service postgres
ERROR: error executing step command 'deploy --all': failed deploying service 'postgres': logging in to registry: could not determine container registry endpoint, ensure 'registry' has been set in the docker options or 'AZURE_CONTAINER_REGISTRY_ENDPOINT' environment variable has been set
.NET Version info
.NET SDK:
Version: 9.0.200
Commit: 90e8b202f2
Workload version: 9.0.200-manifests.a3a1a094
MSBuild version: 17.13.8+cbc39bea8
Runtime Environment:
OS Name: Windows
OS Version: 10.0.26100
OS Platform: Windows
RID: win-x64
Base Path: C:\Program Files\dotnet\sdk\9.0.200\
.NET workloads installed:
[aspire]
Installation Source: VS 17.13.35818.85
Manifest Version: 8.2.2/8.0.100
Manifest Path: C:\Program Files\dotnet\sdk-manifests\8.0.100\microsoft.net.sdk.aspire\8.2.2\WorkloadManifest.json
Install Type: Msi
Configured to use loose manifests when installing new manifests.
Host:
Version: 9.0.3
Architecture: x64
Commit: 831d23e561
.NET SDKs installed:
6.0.428 [C:\Program Files\dotnet\sdk]
8.0.407 [C:\Program Files\dotnet\sdk]
9.0.104 [C:\Program Files\dotnet\sdk]
9.0.200 [C:\Program Files\dotnet\sdk]
.NET runtimes installed:
Microsoft.AspNetCore.App 6.0.36 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 8.0.13 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 8.0.14 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 9.0.2 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 9.0.3 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.NETCore.App 6.0.36 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 8.0.13 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 8.0.14 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 9.0.2 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 9.0.3 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.WindowsDesktop.App 6.0.36 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 8.0.13 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 8.0.14 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 9.0.2 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 9.0.3 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Other architectures found:
x86 [C:\Program Files (x86)\dotnet]
registered at [HKLM\SOFTWARE\dotnet\Setup\InstalledVersions\x86\InstallLocation]
Anything else?
.NET Aspire version: 9.1.0
Microsoft Visual Studio Enterprise 2022 (64-bit) - Current
Version 17.13.1
The text was updated successfully, but these errors were encountered: