New answers tagged

1

I think you may be asking the wrong question. Good practice or bad practice for a Dockerfile, because they have so many different applications, depends on what exactly you do with them. However, if your real question is: How should I deal with this potential for breakage? The answer is, only build your docker image once, as the very first step of your ...


0

Windows services are managed by Service Control Manager. This can be queried, even remotely, using WMI. Most people would probably use a system management software like Nagios. There clearly is an impedance mismatch with kubernetes and the idea of a liveliness query. You could run a web server from inside the console app. See this code as an example.


3

A full answer to your question depends on the complexity of deployment. If you are looking to host a single ASP.Net (core or classic) website, with no additional services, then I would recommend the Azure App Services specifically. When testing Azure App Services, the end-to-end story is really nice: Integration with github or Bitbucket git repositories ...


2

On a very high level, you are not missing out on anything crucial. Docker (and Kubernetes) provide a runtime environment, control plane, deployment, network abstraction etc. which are also provided by cloud vendors. They are different mechanisms but they solve the same problems. With containers, it's a little easier to avoid vendor lock-in. Although AWS and ...


Top 50 recent answers are included