A container image needs somewhere to execute. A registry stores it, while a hosting service decides how processes start, scale and connect to dependencies. Yarrow Drawings has one small API and no existing Kubernetes operations team. Choosing a cluster simply because the image is a container would add an operating boundary without first explaining the requirement.
Compare Azure Container Instances, Container Apps, App Service container hosting and AKS against the workload lifecycle, networking and control needs. Managed hosting can reduce infrastructure work while still leaving code, access and recovery responsibilities with the owner. These are architecture decisions. The local model does not pull or execute images, create an ACR registry, or measure autoscaling. The correct answer depends on the stated operating need rather than a claim that one service is best for every container.
Choose hosting from the workload lifecycle and operating responsibility.