When specifiying <ContainerImageName> periods are being substituted for dashes

[cnickel]

According to the documentation the allows periods and the process doesn't error when they are present, however when the container image is built it substitutes (Normalizes) the periods for dashes. In the container image name I would like to prefix with our Azure container registry.

Would this be possible to do? I can work around by creating another build step to tag after build, but hoping to not have to.

Thanks.

[baronfel]

Interesting - some (many?) container engines don't allow periods at runtime in image names, so we have explicitly chosen to normalize them. We ran into this with at least one registry during initial testing, but I'm struggling to remember if it was Docker or Azure Container Registry that didn't like this. Would you mind describing your target container runtime some more?

[cnickel]

Currently running locally with dockerd via Rancher Desktop. Local repository doesnt seem to mind the periods. The intention of the containers I'm building is to push them to Azure Container Registry and run the images in Azure Container Apps

[baronfel]

We should adjust this and then push up a sample against baronfel/sdk-container-demo to see if or how many of the test registries we have there blow up.