@Artem Mikulich We understand you have created a new App Service Container App and are interested in why you are seeing ~40% memory usage.
We wanted to call out that there is a second site, sitename.scm.azurewebsites.net running on the instance. Also, there are overhead tasks as well that run to support your container. Both of these are running whether or not you have deployed an image to your container. If you deploy a second container to the image, it will also receive its own scm and overhead tasks.
The amount that the scm site and overhead tasks consume will change over time so it will grow and shrink throughout the day. Beyond that, you could see if restarting the App Service relieves some memory pressure.
I want to reassure you that what you are seeing is largely normal and does not appear to be alarming to me. You are using a PaaS product, which requires additional overhead resources to run some of the automated tasks and features that are not required in a traditional IaaS VM.
Beyond that, Microsoft does not really dive deep into the App Service Architecture as this is a PaaS service and we try to offer a managed service as much as possible. For more general App Service Architecture information, we'd suggest you check out this document.
Please let us know if you have further questions or concerns.