PowerShell / PowerShell/PowerShell-Docker
Windows Modules for Windows Nanoimage
Nobody has claimed this yet.
- Dominant language
- Dockerfile
- Stars
- 449
- Forks
- 158
- Avg merge
- 3d 10h
- Merged PRs (30d)
- 1
Description
Summary of the new feature / enhancement
I wanted to manage certificates in a Windows nano image using Powershell, e.g. Import-Certificate
Currently these Windows modules are not included.
My attempts to add them myself were not successful.
Using the PKI module as an example, I copied the files into the nano image and tried to load the module:
Import-Module: Could not load file or assembly 'Microsoft.CertificateServices.PKIClient.Cmdlets, Culture=neutral, PublicKeyToken=null'. The system cannot find the file specified.
Other import methods also produce a similar error:
Failed to load assembly: Exception calling “LoadFile” with “1” argument(s): “Could not load file or assembly ‘C:\tmp\Microsoft.CertificateServices.PKIClient.Cmdlets.dll’. The specified module could not be found.”
I think it might have to do with a lack of dependencies. PKI, for example has:
Referenced Assembly: mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
Referenced Assembly: Microsoft.VisualC, Version=10.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
Referenced Assembly: System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
Referenced Assembly: System.Core, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
Referenced Assembly: System.Xml, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
Referenced Assembly: System.Configuration.Install, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
Referenced Assembly: System.Management.Automation, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
It would be great if these Windows modules were also available.
Proposed technical implementation details (optional)
No response
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.
Research direction
No files, tests, or entry points are named. Start by examining how the Windows Nano images are built and how PowerShell modules and their dependencies are included; done means the requested Windows modules can be imported and used in the image without missing assemblies.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, powershell
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100