How does a windows administrator use containers in practice?

Question

linux

There is a desire to develop in the direction of containerization, devops, etc. But in the IT infrastructure of the organization, now there is an ordinary windows environment, less than a dozen linux servers, there is no development department, but I would like to try and feel it.
Tell me how you use containers in practice, what services can be translated?
And then one gets the feeling that everyone is only doing what they deploy applications for smartphones every day and work in high-tech IT companies, such as Google)

Answer 1

And then one gets the feeling that everyone is only doing what they deploy applications for smartphones every day and work in high-tech IT companies, such as Google)

You won’t believe it, there are a lot of companies that hack them where they should and basically where they shouldn’t at all, explaining this by the security that the container supposedly gives. It’s also a fashion trend, so some stuff containers where they don’t get, and then they tell what a cool and innovative application they have, because docker.
In W2016, they approached containerization pretty well. It can be used for its intended purpose - microservices. When your monolithic application is split into several microservices that perform the same task.

Answer 2

getting into DevOPS from the admin is almost impossible, you need to start serving only Linux servers, get a job at least in web hosting.
Using Docker in Windows is a waste of time, no one will use it in production, train at least on virtual machines, in practice you won’t be able to use it apparently

Answer 3

Containers are "fashionable-stylish-youthful" :)
Just like five years ago they were clouds (which, after all the identified problems, made "puuuu ..." and disappeared somewhere. Of course, they did not disappear anywhere, but the presence of "cloudy service" can now be considered in a very twofold way ... The
same is true of containers - they kind of simplify virtualization ... But in fact they create another layer of entities, which also needs to be managed! Kubernetes did not appear out of nowhere :)
But " invisible hand of the market" :) Everyone wants containers - you have to learn containers :)

Answer 4

Docker is needed for only one thing - delivering the application to the consumer / user with minimal effort.
Moreover, specific settings are transferred to the shoulders of the programmer.
Those. the programmer gives the finished docker container with a working and configured application to the administrator, who deploys it on the production system and everything works (this is ideal).
In reality, usually programmers cannot administer.
Therefore, we came up with the role of dev-ops, which is responsible for supporting the entire container infrastructure.
Plus, he (dev-ops) is usually responsible for testing.
Up to writing tests.

Answer 5

You decide where you want to develop something ... devops is one thing, containerization is another.
DevOps is the automation of building and delivering applications. Learn some CI environment, for example gitlab is popular lately. For CD, something like ansible is also possible. It is unlikely that you will not immediately go to Kube ...
Docker will still be a priority for containers, install a virtual machine (or rather, raise it on one of the physical servers) and go. Again, the gitlab has its own registry, although it’s more correct to raise it separately.
In any case, it is impossible to take and immediately start doing everything. Choose a goal, break it down into tasks and study. Good luck.