Docker image mcr.microsoft.com/windows-insider:10.0.17713.1000 is missing
To have a non-hyperv experience with Windows containers it would be good to have Docker images that fully align with the ISO version. Otherwise people have to run containers in hyperv isolation mode which is slower and also during a docker build it gets much slower. Currently the mcr.microsoft.com/windows-insider is only at 10.0.17711.1000, but no 10.0.17713.1000 is available.How to Install WSL 2 on Windows Server
A couple of months ago Microsoft announced the Windows Subsystem for Linux 2 (WSL 2), which is a successor of the Windows Subsytem for Linux shipped a couple of years ago. WSL 2 is currently available for Windows Insiders running Windows 10 Insider Preview Build 18917 or higher and with the Docker Tech Preview, you can now even run Docker Linux Container directly on WSL 2. With the latest Windows Server Insider Preview build 18945, you are also able to run WSL 2 on Windows Server. In this blog post, I am going to show you how you can install the Windows Subsystem for Linux 2 (WSL 2) on Windows Server. The Windows Subsystem for Linux was already available in earlier versions of Windows Server; however, WSL 2 brings a lot of new advantages. Read more here: https://www.thomasmaurer.ch/2019/08/how-to-install-wsl-2-on-windows-server/SAVE THE DATE: Windows Server 2025 Bug Bash (2/28-3/12)
Join Us and Help Shape the Future of Server Computing Save the dates: Wednesday, February 28th – Tuesday, March 12th, 2024. TL; DR Windows Server 2025 is the latest version of Microsoft's server operating system, designed to power the hybrid cloud and edge computing scenarios. It introduces new features such as Hotpatching for Azure Arc-enabled servers, Next Generation Active Directory & SMB, Mission Critical Data & Storage, Hyper-V & AI, Container Flexibility, Upgrade via Windows Update and Modern Desktop Experience. You can help us test and improve these features by joining the Windows Server 2025 Bug Bash, starting from February 28th to March 12th. What is a Bug Bash? A bug bash is a collaborative event where users, developers, and enthusiasts come together to identify and report bugs in the product. It’s an opportunity to explore new features, test functionalities and contribute to improving the software's quality. Timeline for the Bug Bash The Windows Server 2025 Bug Bash will run from February 28th to March 12th. During this period, you can try out new features and functionalities of Windows Server 2025 and provide your feedback. How to Participate To participate in the Windows Server 2025 Bug Bash, you need to do the following: Update your system to the latest preview build of Windows Server 2025. See: Announcing Windows Server Preview Build 26063 - Microsoft Community Hub If you are opted into Server Flighting, accept the latest flight from the Server Preview Canary channel. Learn more: Welcome to Windows Insider flighting on Windows Server - Microsoft Community Hub Download the latest Server Insider build from Download Windows Server Insider Preview (microsoft.com) Access the latest preview of Windows Server Azure Edition from the Microsoft Server Operating Systems Preview offer in Azure. Sign in to the Feedback Hub app on your Windows Server 2025 machine. You can find the app in the Start menu. Please update the app to latest available version by clicking on Settings > Updates > Check for Updates button in the app. Navigate to the Quests section in the Feedback Hub app. You will see a list of quests that cover various features and scenarios for Windows Server 2025. Pick a quest of your choice and follow the instructions. You will be asked to perform certain tasks and check for expected outcomes. Send us your feedback using the Feedback Hub app. You can report any bugs, issues or suggestions that you encounter. You can also attach screenshots, videos or logs to your feedback. In addition to the quests, we welcome your feedback on your experience. Feature Highlights We’re excited to introduce several new and enhanced features in Windows Server 2025: Hotpatching for Azure Arc-enabled servers This feature allows seamless updates and patches for servers running Azure Arc, ensuring minimal downtime and improved reliability. Next Generation Active Directory & SMB Windows Server 2025 introduces enhancements to Active Directory, including support for larger page sizes, NUMA optimizations, LDAP TLS 1.3 and improved security for confidential attributes. Additionally, SMB (Server Message Block) benefits from performance improvements. Mission Critical Data & Storage Windows Server 2025 prioritizes robust data management and storage solutions. It ensures high availability, scalability and reliability for critical workloads and applications. Hyper-V & AI Hyper-V, Microsoft’s virtualization platform, has been updated to enhance performance, security and scalability. Additionally, Windows Server 2025 integrates AI capabilities for intelligent workload management and resource optimization. Container Flexibility Windows Server 2025 continues to support containers, allowing developers to build, deploy, and manage applications efficiently. Whether you are using Docker or Kubernetes, the platform provides flexibility and compatibility. Upgrade via Windows Update Simplified upgrade paths make transitioning to Windows Server 2025 smoother. You can now update directly via Windows Update, reducing complexity and downtime. Modern Desktop Experience Windows Server 2025 offers an improved desktop experience making it easier for administrators and users to navigate and manage server environments. Check out Modern Desktop Experience in: Privacy settings at first login (when installing from ISO) Start, Taskbar, and Settings Settings > Accounts (there are several new experiences) Terminal and Winget (Winget will install apps from the Store and GitHub) Task Manager WiFi and Bluetooth (if running on equipped hardware) Battery features and sleep We hope you enjoy participating in the Windows Server 2025 Bug Bash and look forward to hearing your feedback. Thank you for helping us shape the future of server computing. Diagnostic and Usage Information Microsoft collects this information over the internet to help keep Windows secure and up to date, troubleshoot problems, and make product improvements. Microsoft server operating systems can be configured to turn diagnostic data off, send Required diagnostic data, or send Optional diagnostic data. During previews, Microsoft asks that you change the default setting to Optional to provide the best automatic feedback and help us improve the final product. Administrators can change the level of information collection through Settings. For details, see http://aka.ms/winserverdata. Also see the Microsoft Privacy Statement. Terms of Use This is pre-release software - it is provided for use "as-is" and is not supported in production environments. Users are responsible for installing any updates that may be made available from Windows Update. All pre-release software made available to you via the Windows Server Insider program is governed by the Insider Terms of Use.nanoserver-insider image has non-admin user as default?
I just want to mention that the microsoft/nanoserver-insider image has the non-admin "ContainerUser" account as default. Is this intented? Running containers as non-admin is a good thing, but this default sometimes result in some difficulties while building Docker images based on nanoserver-insider. In a golang+git nanoserver image I had to use a workaround to switch to ContainerAdministrator, setting the machine PATH variable, and switch back: https://github.com/StefanScherer/dockerfiles-windows/blob/c3a6dce28d325e25d3ed993e7d2b4fabd99c3b81/golang/Dockerfile#L45-L47 Otherwise we can only set the users's PATH (setx without /M option): https://github.com/StefanScherer/dockerfiles-windows/blob/b9c944fdcf8ceb936d41a48837afaba8fd92b372/node/6.11/nano/Dockerfile#L41 While creating a Docker image for the Docker swarm visualizer I once again had problems while "npm run dist" os I also had to prepend a "USER ContainerAdministrator" to have write access to C:/app - see the Dockerfile example in https://github.com/dockersamples/docker-swarm-visualizer/pull/87#issue-260104486 So the question is if the nanoserver-insider image shouldn't have a value for the user just as the windowsservercore-insider image. If someone wants to change the user, it is possible by adding a line USER ContainerUser in the Dockerfile for any Windows image.
mcr.microsoft.com/windows-insider image is missing Get-WindowsFeature cmdlet
Hello, I have a problem with the new windows-insider Docker image. The PowerShell command Get-WindowsFeature does not work at all. $ docker run mcr.microsoft.com/windows-insider:10.0.17709.1000 powershell -Command Get-WindowsFeature Get-WindowsFeature : The term 'Get-WindowsFeature' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again. At line:1 char:1 + Get-WindowsFeature + ~~~~~~~~~~~~~~~~~~ + CategoryInfo : ObjectNotFound: (Get-WindowsFeature:String) [], CommandNotFoundException + FullyQualifiedErrorId : CommandNotFoundException But with the smaller windowsservercore-insider it works: $ docker run mcr.microsoft.com/windowsservercore-insider:10.0.17709.1000 powershell -Command Get-WindowsFeature Display Name Name ------------ ---- [ ] Active Directory Certificate Services AD-Certificate [ ] Certification Authority ADCS-Cert-Authority [ ] Certificate Enrollment Policy Web Service ADCS-Enroll-Web-Pol Is there a plan to add these PowerShell commands to add other Windows features?
