-
Notifications
You must be signed in to change notification settings - Fork 67
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CCG Custom Plugin #544
Comments
Thank you for creating an Issue. Please note that GitHub is not an official channel for Microsoft support requests. To create an official support request, please open a ticket here. Microsoft and the GitHub Community strive to provide a best effort in answering questions and supporting Issues on GitHub. |
@hordurmarhafsteinsson Thanks for sharing another error with CCG. We've brought up this Issue to the team that owns CCG and will update this thread when we have something to share. |
Would you mind opening a ticket with Microsoft support? The CCG team prefers to go through the official mechanisms. |
This issue has been open for 30 days with no updates. |
1 similar comment
This issue has been open for 30 days with no updates. |
What is your question?
I have been setting up a custom CCG plugin on my local machine to run a windows container as non-domain joined.
When starting the container, using the following command:
docker run -it --security-opt "CredentialSpec=file://gmsa.json" mcr.microsoft.com/windows/servercore:ltsc2022 powershell
I can see the following message in the Microsoft-Windows-Containers-CCG/Admin log:
Container Credential Guard instantiated the plugin: {3C0BED28-38FC-42A9-A6AC-967A4839DF61}
However the container doesn't start, but just gives the following error:
docker: Error response from daemon: hcs::CreateComputeSystem 566516d3912884945d031f7982c6fea1977f22c5d07d40766173354444fb7fc5: winapi error #3489661095.
What can I do to get a more detailed information regarding the error, as it is quite difficult to understand what is failing.
Configuration:
The text was updated successfully, but these errors were encountered: