My question has to do with the posture of Azure container groups. I'm comfortable working with Docker images and and deploying those in a Kubernetes environment. I'm new to Azure. I have a container running in a container group. I deployed it with a JSON template, through the web portal. I can bash into it with the Connect option in the web portal and make some changes. In a Docker environment, I could then commit those changes to an image and push that to my repository. I want to know how to do the same with a container running in a container group in Azure. I'm getting the sense that it's more like a Kubernetes environment, where the expectation is that you've already built your image to spec and now you're just deploying it and using it as-is (changes are made and committed elsewhere). However, it also seems like this should be a really basic functionality of the service Microsoft is offering here. What's the deal?
Thanks