powershell/7.4.2 package update

[octo-sts]

[debasishbsws]

Looks like the dotnet sdk has another release but that is not included in the dotnet monolith repository we are using here.

[debasishbsws]

In the official release we have more than one SDK version https://dotnet.microsoft.com/en-us/download/dotnet/8.0

Should we break the dotnet package into dotnet-runtime and dotnet-sdk

[debasishbsws]

Though the docs suggest to build dotnet v8+ from the repo dotnet/dotnet but we can use the dotnet/installer which we were using for dotnet-6 and dotnet-7

[debasishbsws]

This will take time as it may need #17580

[debasishbsws]

It will get Fix after #17699 get merged into main

[TaylorBloom129]

@rawlingsj to follow up with Dimitri

[debasishbsws]

The issue for powershell build failure is connected to #17580 Dotnet sdk version mismatch it requires version 8.0.204 but in wolfi we have dotnet-8-sdk 8.0.104.

I have tried to separate the SDK from the main package in #17699 and the powershell is building perfectly with that. But there will be incompatibility issue.

Yesterday I tried to build the dotnet-8 package from the dotnet/installer repo as they provide the new SDK v8.0.204 but could not able to build it correctly.

[rawlingsj]

Ok thanks @debasishbsws, I don't have any knowledge of powershell so we might need some help from @xnox or @smoser 🙏

[lambdaclan]

Hello there. I am not sure if this is the right place to report this, but I would like to bring an issue related to the PowerShell package to your attention. I am relatively new to using Wolfi images in containers, so I am not 100% familiar of the relation between Wolfi and Alpine packages, but it seems like the Wolfi PowerShell package is incomplete in the same fashion the Alpine package is.

Basically, the provided PowerShell package is missing quite a few of the built-in modules which in turn significantly reduces usability of the shell. There is already an upstream issue here PowerShell/PowerShell#20143.

The good news is that there is a workaround. If you install PowerShell via dotnet as a global tool then all modules become available.

To reproduce the issue you can use the following as a reference:

apk add powershell
pwsh
Get-Module -ListAvailable

apk add dotnet-8-sdk
dotnet tool install --global PowerShell
~/.dotnet/tools/pwsh
Get-Module -ListAvailable

I am not really sure what the best course of action is at this moment, maybe just wait for upstream fix?

If I need to create a proper issue under a different repo or something please let me know.

Thank you.

[rawlingsj]

Thanks @lambdaclan! Appreciate the info. We do have an issue tracker on this repo but given we have a problem with powershell with this PR let's see if we can get some thoughts from others.

@smoser don't suppose you got anywhere with looking at Powershell?

[octo-sts]

superseded by #22270