# Preffered way to deploy icinga2 in 2024 **URL:** \ **Category:** Icinga 2\ **Tags:** docker, icinga2\ **Created:** [October 4, 2024, 3:04pm UTC](https://community.icinga.com/t/preffered-way-to-deploy-icinga2-in-2024/14163 "2024-10-04T15:04:58Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![moreamazingnick](https://community.icinga.com/user_avatar/community.icinga.com/moreamazingnick/32/7725_2.png) [@moreamazingnick](https://community.icinga.com/u/moreamazingnick)\ **Post date:** [October 5, 2024, 5:12am UTC](https://community.icinga.com/t/preffered-way-to-deploy-icinga2-in-2024/14163/2 "2024-10-05T05:12:24Z")
My preferred way is to run it baremetal and using packages. Here are some thoughts: - severe problems with your hypervisor → no monitoring - severe problems with your kubernetes cluster → no monitoring - severe problems with docker → less help from the community - selfmonitoring the icinga-master using docker → I think you need a container with more privileges or you are monitoring for example the docker disk and not the system disk. - here is a thread about icinga in a [container](https://community.icinga.com/t/dockerizing-icinga-any-benefits/3546) but it is quite old. - from my point of view docker is great for testing, like icingaweb2, or icingaweb2-modules with various php, influxdb versions. - If you have severe problems with your infrastructure and your monitoring is affected by that, it gets a lot harder to find the issues. - here is the blogpost of [ansible-collection-icinga](https://icinga.com/blog/2022/04/07/introduction-of-the-ansible-collection-icinga/) - and here is an interesting talk on icinga in kubernetes: [![](https://community.icinga.com/uploads/default/original/2X/0/01ffad5d817faa59c47334f1d8f4eae07f26bb83.jpeg "Icinga Camp Berlin 2023: The Times They Are A'Changing: Icinga 2 on Kubernetes by Daniel Bodky") ](https://www.youtube.com/watch?v=7BY9ZT2UAw0) --- _[View the full topic](https://community.icinga.com/t/preffered-way-to-deploy-icinga2-in-2024/14163)._