WSL Containers (wslc) -- support gMSA or other AD / Kerberos identity a la CCG (container credential guard)
@craigloewen-msft is already working on this.
Since Jul 7, 2026.
- Dominant language
- C++
- Stars
- 33.7k
- Forks
- 1.8k
- Avg merge
- 3d 17h
- Merged PRs (30d)
- 116
Description
Is your feature request related to a problem? Please describe.
There is no way to have a container inherit the running identity of the invoking user, or a different defined identity on the Windows host or in the Active Directory domain.
To get such an identity requires providing the container with credentials and using them over the container network, sometimes requiring specific system packages or utilities installed (kinit).
Describe the solution you'd like
I'd like to be able to run a container and have it optionally inherit the identity of the running user.
This is especially useful in interactive scenarios where a user wants to run an application or utility as themselves, with all the same permissions and rights that they have in their running session.
I'd like to be able to run a container and have it optionally run with the identity of a defined user or gMSA, as can be done with Windows containers.
This is most useful in server environments to run containerized services under a service account identity (as it is used today with Windows containers).
Additional context
While the Microsoft feature is currently only available for Windows containers, cloud providers have added support for AD gMSA identity to linux containers for a while now, so there is some precedent.
AWS provides their linux credential-fetcher daemon under the Apache-2.0 license:
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.