Problem
Currently it's not possible to specify the user inside a container. This is problematic for containers that need to be tested to run as non default user / non root environment. This is also a problem for images that explicitly specify user via USER <name> directive when used in conjuction with WithResourceMapping which copies all files into container as ROOT, preventing their manipulation by the user the container is running under
Solution
Add WithUser(string name)toContainerBuilderthat would map to--user argument ofdocker run`.
Benefit
All proper testing of containers that need to run as non standard user.
Alternatives
No good alternatives have been identified
Would you like to help contributing this enhancement?
Yes
Problem
Currently it's not possible to specify the user inside a container. This is problematic for containers that need to be tested to run as non default user / non root environment. This is also a problem for images that explicitly specify user via
USER <name>directive when used in conjuction withWithResourceMappingwhich copies all files into container asROOT, preventing their manipulation by the user the container is running underSolution
AddWithUser(string name)toContainerBuilderthat would map to--userargument ofdocker run`.Benefit
All proper testing of containers that need to run as non standard user.
Alternatives
No good alternatives have been identified
Would you like to help contributing this enhancement?
Yes