Thanks for reply! Yes you are correct. Also you may want to know ; Web App for Containers is catered more towards developers who want to have more control over, not just the code, but also the different packages, runtime framework, tooling etc. that are installed on their containers. This offering is essentially bringing years worth of Azure App Service PaaS innovations to the community, by allowing developers to just focus on composing their containers without worrying about managing and maintaining an underlying container orchestrator. Customers of this offering prefer to package their code and dependencies into containers using various CI/CD systems like Jenkins, Maven, Travis CI or Azure DevOps, alongside setting up continuous deployment web hooks with App Service.
You may also refer to this thread explaining Difference between Container Instances and Container for Webapps might be helpful
If the above answer was helpful, kindly do ‘Accept as answer' and/or ‘Vote as helpful’ the post for benefitting the other users with a similar issue.