![Lansweeper docker](https://cdn1.cdnme.se/5447227/9-3/14_64e61dfbddf2b36505b4c7c8.png)
![lansweeper docker lansweeper docker](https://lh3.googleusercontent.com/-gkFQBAjsa1o/X4JGQSwdjYI/AAAAAAAACBs/_JA-CaOTfCoaa_ZLl0ZNujdksbdRuwIZQCLcBGAsYHQ/w1200-h630-p-k-no-nu/image.png)
The work started with the construction of the Windows Dockerfile, where I already hit an issue with Docker refusing to switch to Windows Containers… Guess we know how much they care about those? The Web interface can run in a container (see below) but it’s not supportedĪs such, I’ve decided to start with what I assume would have been the easiest part of the project: containerizing the Lansweeper Web component and running it in Azure Container Services integrated with the VNET where the rest of the components are running and with a load balancer in front to load balance the traffic.The Scanning server doesn’t work properly in a container and is not supported:.The database cannot be run on Azure SQL or SQL Managed Machine, only SQL VM, and the support has been asked by customers in 2018:.
![lansweeper docker lansweeper docker](https://nakedsecurity.sophos.com/wp-content/uploads/sites/2/2020/05/Docker-Logo-White-RGB_Vertical-BG_0.png)
So, the initial idea of this project was to do what Lansweeper hasn’t done in years and try to modernize the Lansweeper solution by running parts of it in PAAS/SAAS environments.īasically Lansweeper hasn’t updated their main installation for use in the Cloud, which means that:
![Lansweeper docker](https://cdn1.cdnme.se/5447227/9-3/14_64e61dfbddf2b36505b4c7c8.png)