[Enhancement]: Start Ryuk as a privileged container

[taspeotis]

Problem

I'm using podman in lieu of docker. It seems to work fine with TestcontainersSettings.ResourceReaperEnabled = false; however this is not ideal. Without that setting it fails with permission errors.

I have podman running as rootful, I believe if testcontainers-dotnet had a similar option to ryuk.container.privileged = true (to create it with --privileged) it would work completely.

https://www.testcontainers.org/features/configuration/#customizing-ryuk-resource-reaper

containers/podman#14238 (reply in thread)

Solution

Some way to create Ryuk as privileged, for podman and whatever other reasons the testcontainers "Customizing Ryuk resource reaper" documentation refers to:

In some environments ryuk must be started in privileged mode to work properly

Benefit

Works with podman

Alternatives

TestcontainersSettings.ResourceReaperEnabled = false;

Would you like to help contributing this enhancement?

Yes

[HofmeisterAn]

Indeed, ryuk.container.privileged is not yet supported. We need to add the custom configuration property first, similar to 45a8935. Afterwards with can update the ResourceReaper builder configuration. I suggest two separate PRs. Would you like to add the property first?

[taspeotis]

Thanks, I'll see what I can do in the next few days.

[taspeotis]

Sorry I wasn't able to contribute this but thank you for adding it!