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

[bangzhuzhu]

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?

[rimelek (Ákos Takács)]

As I wrote it in the other topic:

Why lcow not support --privileged

docker: Storage Driver: windowsfilter (windows) lcow (linux) I think the lcow is a mode that docker build a vm to run linux container, so get the host permission to create a privileged container is achievable way. So I want to know some more detailed answer or a way to find answer. Thank you.

lcow was an experimental project. I don’t think you should use that today.

As for the question, to be honest, I wasn’t sure about the answer, so I should probably learn more about that, but I searched for “docker privileged cap-add” on Google and found this:

Difference between `--privileged` and `--cap-add=all` in docker

Without that post on StackOverflow, I would have said that: even if --security-opt and --cap-add are not enough, you can probably achieve the same result without --privileged. In your case I am not sure about that. If --privileged was not implemented, I guess it is because the alternatives are not implemented either.

I recommended some other ways in the other topic that you can use instead of lcow.

[bangzhuzhu]

Thank you, I just wanted to do some experiments to figure out a way to start a linux container(k3s) in windows. This container has to use privileged mode, I’m trying to bypass it. If it can’t achieve, I still want to know why it’s possible.