Microsoft support recommended opening this issue here.
We have found out that in the use case that a container is created specifying a git repository as volume, and in such request, the "revision" is pointing to a nonexisting git commit, the container ends in a status "waiting" forever instead of moving to a failed state and have a clear explanation on what happened.
The issue is misleading especially for teams who operate ACI Containers and they receive code handled by another team, any operation done by the other team may break the container without the first ones understanding what's happening.
Microsoft support recommended opening this issue here.
We have found out that in the use case that a container is created specifying a git repository as volume, and in such request, the "revision" is pointing to a nonexisting git commit, the container ends in a status "waiting" forever instead of moving to a failed state and have a clear explanation on what happened.
The issue is misleading especially for teams who operate ACI Containers and they receive code handled by another team, any operation done by the other team may break the container without the first ones understanding what's happening.