Why lcow not support --privileged

[rimelek (Ákos Takács)]

I have just heard about lcow yesterday, and today I realized I heard about it before, but I totally forgot about that, since I have never used that. Now we have WSL2 on Windows 10 and 11 and you can run Virtual Machines on Windows Server or use Windows Server 2022 with WSL2. I have learned it from @vrapolinario

Linux container support on Windows servers

Not sure this is allowed, but for anyone interested on Linux containers on Windows Server, I’d love to chat more and understand the scenario. Please reach out. Here’s a workaround that is supported: You can use Hyper-V to install a Linux VM on Windows Server and run your containers there. This is not much different than what WSL does. Here’s another workaround that is supported: You can use WSL2 on Windows Server 2022 now: WSL2 now available on Windows Server 2022 (microsoft.com) Please note t…

As far as I know, lcow was an experimental project and discontinued. The privileged mode means you have unlimited access to the kernel. I don’t know how lcow worked, but maybe the nature of lcow did not allow to implement it easily. Buy the way, the privileged mode is something that was implemented long ago, and Justin Cormack, the CTO of Docker said it should not even exist, but it was required then. Well, I don’t remember his exact words (I think it was on DockerCon or in a YouTube video), but this leads us to your next question in the other topic:

Can --privileged perfectly replace all by --security-opt xxx and --cap-add xxx?

I want to run a specific container(k3s) need privileged mode in a windows docker with(lcow feature), but windows do not support --privileged. so Is there any way to replace it with --security-opt and --cap-add?