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
If a publish to a registry fails, the status still indicates succes
🔍 Steps to Reproduce the Bug
Set a registry that is invalit
aspirate generate
OBSERVE: publish failed but the aspirate status gives me ✔️ vibes
/usr/local/share/dotnet/sdk/8.0.100/Containers/build/Microsoft.NET.Build.Containers.targets(202,5): error : at
Microsoft.NET.Build.Containers.Tasks.CreateNewImage.PushToRemoteRegistryAsync(BuiltImage builtImage, SourceImageReference
sourceImageReference, DestinationImageReference destinationImageReference, CancellationToken cancellationToken) in
/_/src/Containers/Microsoft.NET.Build.Containers/Tasks/CreateNewImage.cs:line 199
[/Users/timheuer/Projects/aspire1/aspire1.ApiService/aspire1.ApiService.csproj]
(✔) Done: Building and Pushing container for project apiservice
🧯 Possible Solution
Observe the error state of previous commands and mirror correct state
The text was updated successfully, but these errors were encountered:
That's strange!
Is that the current release of dotnet, or a preview?
Mine when I do that raises error 'CONTAINER1013' - whats strange is it says the same line number as the error yours throws on - at that target
For instance - this is me throwing an image at google lol
🔥 Bug Description
If a publish to a registry fails, the status still indicates succes
🔍 Steps to Reproduce the Bug
aspirate generate
OBSERVE: publish failed but the aspirate status gives me ✔️ vibes
🧯 Possible Solution
The text was updated successfully, but these errors were encountered: