Container images not deprecated
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
Start by reviewing the MCR artifact page and the PowerShell-in-Docker installation documentation linked in the issue. Confirm which published images lack deprecation status and determine the repository or registry entry that controls it; done means the PowerShell images are marked deprecated in MCR.
Written by the indexing model from the issue text.
Description
Prerequisites
- Write a descriptive title.
- Make sure you are able to repro it on the latest released version
- Search the existing issues.
- Refer to the FAQ.
- Refer to Differences between Windows PowerShell 5.1 and PowerShell.
Steps to reproduce
It appears that the Powershell images published to MCR were intended to be deprecated, but there is no indication of this within MCR, while they have not been updated in any way in the last 6 months:
- https://mcr.microsoft.com/en-us/artifact/mar/powershell/about
- https://learn.microsoft.com/en-us/powershell/scripting/install/powershell-in-docker?view=powershell-7.5#use-powershell-in-a-container
The install documentation was updated to reflect that end users should switch to the SDK image and that these would be marked deprecated, but since no deprecation has happened within MCR, this state is unclear to anyone who has been referencing these images without finding the corresponding install documentation.
Expected behavior
The container images for Powershell should be marked as deprecated within MCR.
Actual behavior
The MCR images appear to be valid to use from the README with them.
Error details
Environment data
https://mcr.microsoft.com/en-us/artifact/mar/powershell/about
Visuals
No response
- Dominant language
- Dockerfile
- Stars
- 449
- Forks
- 158
- Avg merge
- 3d 10h
- Merged PRs (30d)
- 1
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.
More from PowerShell/PowerShell-Docker
-
Git OpenIssue-Enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
PowerShell/PowerShell-Docker#857 ·
-
Issue-Enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 48/100
PowerShell/PowerShell-Docker#854 ·
-
Issue-Enhancement
Difficulty 5/5 Over a week Newbie friendliness 25/100
PowerShell/PowerShell-Docker#853 · 6 comments · 17 reactions ·
-
Issue-Enhancement
Difficulty 3/5 1-2 days Newbie friendliness 45/100
PowerShell/PowerShell-Docker#851 · 2 comments · 2 reactions ·
-
Difficulty 4/5 3-5 days Newbie friendliness 28/100
PowerShell/PowerShell-Docker#847 ·
All issues in PowerShell/PowerShell-Docker
Similar issues
-
A cancelled tests run makes the coverage comment workflow fail and reports it as a red check on main Openarea: ci bug perceived difficulty: 3
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Nitjsefnie-Harness-Commons/daedalus#921 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
crossplane/crossplane#7859 ·
-
Product: Terraform (AVM) Topic: Networking (HS) :globe_with_meridians:
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Azure/Azure-Landing-Zones#4282 · 1 comment ·
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
-
bug carvel-triage
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
carvel-dev/kapp-controller#1861 ·