Publishing a solution filter with multiple container enabled projects loops indefinitely on pipeline

[csjall]

I have a handful of ASP.NET Core projects in a solution filter. In each project file I define some specific environment variables and repository properties.

<PropertyGroup>
   ...
  <ContainerRepository>$(BaseContainerRepository)/my-service</ContainerRepository>
</PropertyGroup>

<ItemGroup>
  <ContainerEnvironmentVariable Include="ASPNETCORE_HTTP_PORTS" Value="5000" />
</ItemGroup>

I define some shared properties in Directory.Build.props.

  <PropertyGroup>
    <ContainerRegistry Condition=" '$(ContainerRegistry)' == '' ">localhost:5000</ContainerRegistry>
    <BaseContainerRepository Condition=" '$(BaseContainerRepository)' == '' ">base</BaseContainerRepository>
    <ContainerImageTags Condition=" '$(ContainerImageTags)' == '' ">1.2.3</ContainerImageTags>
  </PropertyGroup>

When I run dotnet publish <solution filter> --runtime linux-x64 /t:PublishContainer locally I see the services built, containers created, and published to my local container repository. When I run the same command as part of my AzDo pipeline then I see some different behavior. On occasion the pipeline run will succeed and publish the containers to the specified registry. On other occasions the pipeline run will not succeed, instead rebuilding the same batch of projects indefinitely. Eventually the pipeline job times out and the run is cancelled.

The biggest challenge is the complete lack of debugging information. Is there a way to figure out why the dotnet publish command is looping indefinitely? Is there some logging information that can be enable to show what the container build is attempting to do?