Containers Archives

Winsage

July 1, 2026

Bottles is how you should actually run Windows apps on Linux

Wine enables users to run Windows applications on Linux by translating Windows calls into POSIX calls. It has evolved significantly, especially with contributions from Valve's Proton project, but can be complex and unpredictable, leading to potential glitches with updates. Bottles enhances this experience by creating isolated containers for each application, allowing users to run specific versions of Wine tailored to individual applications. This approach improves compatibility and organization, as users can group applications with similar settings. Bottles also features Eagle, a tool that recommends optimal Wine setups, and allows easy backup and restoration of configurations, ensuring a clean system.

Winsage

June 28, 2026

Microsoft denies WSL 3 exists, reveals Windows 11’s WSL Containers ship next week

Microsoft has clarified that there is no WSL 3 in development, as stated by Craig Loewen, the Product Manager for the Windows Subsystem for Linux (WSL). The confusion arose from articles discussing a new feature called WSL Containers, which will be launched soon. WSL allows users to run Linux environments on Windows without dual-booting, while WSL Containers enable the creation and management of Linux containers directly within Windows, eliminating the need for third-party tools like Docker Desktop. WSL 1, introduced in 2016, served as a translation layer for Linux system calls, and WSL 2, launched in 2019, included a full Linux kernel in a lightweight virtual machine. WSL Containers is an enhancement to WSL, allowing developers to build, run, and deploy containers directly from Windows using the wslc.exe command. This feature is part of Microsoft's strategy to make Windows a more accessible platform for running Linux workloads, helping to retain developers who might consider switching to other operating systems.

Winsage

June 23, 2026

Why is Windows 11 so disliked by programmers – and can Microsoft do anything to change things?

Windows is experiencing a decline in favor among developers, with many preferring macOS and Linux for coding. Although nearly half of developers (49.5%) primarily work on Windows, this is often due to organizational mandates rather than personal preference. Developers interviewed did not select Windows as their preferred environment, citing concerns about Microsoft's developer experience, cumbersome tools, and security issues. The Windows Subsystem for Linux (WSL) allows developers to run Linux environments on Windows 11, addressing some compatibility issues. However, there is a consensus that Microsoft should enhance WSL and align Windows more closely with Linux to attract more developers. Critics also point to the intrusive nature of ads and upselling in Windows 11 as detracting from the developer experience.

Tech Optimizer

June 22, 2026

pgAdmin 4 Released With Fixes for Seven Security Vulnerabilities and New Features

pgAdmin 4 version 9.16 has been released, featuring 64 bug fixes and addressing seven security vulnerabilities (CVE-2026-12044 to CVE-2026-12050). Key vulnerabilities include SQL injection flaws and cross-site scripting issues. CVE-2026-12044 involved SQL injection risks in dialog templates, while CVE-2026-12045 allowed attackers to bypass read-only transaction restrictions in the AI Assistant feature. Authentication issues were fixed in CVE-2026-12046, and client-side vulnerabilities were addressed in CVE-2026-12048 and CVE-2026-12047. Additional vulnerabilities included an open redirect in multi-factor authentication (CVE-2026-12049) and another SQL injection flaw in restore point functionality (CVE-2026-12050). Usability improvements include colorized panel headers, middle-click tab closing, and enhancements to OAuth2 login. The release supports new PostgreSQL storage parameters and includes dependency upgrades. Stricter access controls have been enforced, and pgAgent has been marked for removal. The update is available for download on multiple platforms.

AppWizard

June 21, 2026

Marathon players are amassing way too much loot in Season 2, and the primary cause is a mystery: ‘We’re still unravelling the source’

Season 2 of Marathon began with technical issues and a free-to-play week, but introduced new features like the Night-time Dire Marsh map and Sponsored Survival mode. Players experienced unexpected ease in progression, leading to an influx of treasures and a disrupted in-game economy. Bungie acknowledged that player progression and access to power in Season 2 moved much faster than in Season 1, with players accumulating wealth comparable to weeks 11 and 12 of Season 1 by the second week of Season 2. Contributing factors included bugs causing guaranteed gold drops, early access to Sponsored Kits, and lucrative chests in the Complex Control area. Bungie is investigating the source of excessive loot, as it was not observed in internal playtests. Temporary adjustments have been made, such as disabling boosted containers and reducing Cradle XP rates, with plans to reinstate previous conditions later in the season.

Winsage

June 19, 2026

Windows Platform Security and the Race to Secure AI Agents

Microsoft has introduced the Microsoft Execution Containers (MXC) SDK to establish Windows as a reliable operating system for autonomous agents, focusing on containment, identity, and manageability. The MXC framework serves as a policy-driven execution layer for agents on Windows and Windows Subsystem for Linux (WSL), allowing developers to set access permissions using JSON or TypeScript. It employs process and session isolation for agent containment and identity. Future enhancements will include micro-VM support for high-risk tasks and integration with Windows 365 for cloud PC workloads. IT teams can manage MXC policies through Entra ID and Intune, while Defender and Purview provide protection and observability. The MXC framework is built on Microsoft's security initiatives, including Secure Boot and passwordless sign-in, allowing agents to inherit a secure foundation. However, early commentary expresses caution regarding MXC's perception as a comprehensive security solution, noting issues with overly permissive policies and the lack of outbound network filtering. Other platforms, such as Linux, are also enhancing security for agents with kernel-level isolation and secure environments like NVIDIA's OpenShell runtime. Various projects are focusing on agent sandboxes within Kubernetes, employing technologies like gVisor and Kata Containers for isolation. Overall, no singular dominant platform security model for AI agents has emerged, with Windows' MXC still considered nascent compared to existing solutions in Linux and Kubernetes ecosystems.

Winsage

June 9, 2026

Microsoft Makes Windows 11 an Agentic Platform

Microsoft announced a suite of agent-centric features for Windows 11 at the Build 2026 conference, introducing the Microsoft Agent Platform for local AI agents. This includes enhanced integration with Microsoft Foundry, GitHub, and the M365 suite. The developer documentation covers local agent runtimes and isolation patterns, highlighting the Microsoft Execution Containers SDK and Entra Agent ID. Enterprise controls like Intune and Agent 365 are also featured. The upcoming Copilot Actions will allow agents to interact with local files and applications, aimed at improving workflows. Microsoft is addressing security concerns with resources outlining strategies to mitigate risks such as cross-prompt injection. Industry commentary indicates a growing discussion about privacy and security in relation to these changes.

Winsage

June 9, 2026

Hybrid AI Agents, Orchestration, and the Real Reason Microsoft is Fixing Windows 11 ⭐

Over the past weekend, the author reviewed session videos from Build 2026, focusing on Windows 11. The sessions were categorized into three areas: Windows app development, developer productivity, and agentic AI. The introduction of hybrid agents, which combine local AI sub-agents, was a notable development. Microsoft's partnership with Qualcomm led to the launch of Windows 10 on Arm-based PCs branded as Always Connected PCs, which evolved into Copilot+ PCs with Nuvia-powered chips for Windows 11. The Copilot+ PCs emphasize on-device AI experiences through powerful neural processing units (NPUs). The introduction of second-generation Snapdragon X2-based PCs is underway, although adoption is slower than expected. Microsoft confirmed that Windows 11 will integrate AI agents, including local AI agents and hybrid agents. The capabilities of local AI models are being enhanced, and Windows AI APIs will now support CPUs and GPUs. New Nvidia chipsets will enable large language models to run locally on PCs. The orchestration of local and cloud AI components is essential for efficient AI workload management. Microsoft is addressing user pain points to support a robust local foundation for hybrid AI, aiming to improve Windows 11 overall.

Winsage

June 7, 2026

4 Windows 11 tools from Build 2026 that signal what’s coming next for the OS

Microsoft announced several key updates at the Build 2026 developer conference, particularly for Windows 11: 1. Coreutils: This suite brings familiar Linux command-line utilities to Windows 11, allowing developers to use commands like ls, cp, and mkdir natively without third-party solutions. It can be installed via GitHub or the Windows Package Manager. 2. WSL Containers: This feature introduces a built-in container runtime for running Linux containers on Windows 11, eliminating the need for external platforms like Docker. It utilizes a command-line tool called "wslc.exe" and allows for OCI-compatible Linux containers. 3. Intelligent Terminal: This feature integrates AI agents into the terminal, providing context-aware assistance for developers. It can be installed via the Microsoft Store or Command Prompt. 4. Windows Developer Configurations: This configuration file for the Windows Package Manager automates the installation of essential developer tools and settings, streamlining the setup process for new development or testing machines.

Tech Optimizer

June 6, 2026

PostgreSQL Dump and Restore: The Complete pg_dump Guide

pg_dump is a utility for exporting a PostgreSQL database into a file, which can be restored on the same or different servers. It exports a single database's tables, views, sequences, functions, indexes, triggers, and in-database grants but does not include roles, tablespaces, or server-level configurations. To capture global objects, pg_dumpall --globals-only should be executed prior to the per-database dump. pg_dump requires CONNECT and SELECT privileges on all tables and sequences within the target database, and a dedicated backup role is sufficient for single-database dumps, while superuser access is needed for global objects. pg_dump supports various output formats: plain SQL (.sql), custom binary (.dump), directory of files, and tar archive (.tar), each with different capabilities for restoration and compression. The custom format allows for selective and parallel restoration. For non-interactive use, credentials can be stored in a .pgpass file or passed via the PGPASSWORD environment variable. Restoration methods depend on the dump format: psql is used for plain SQL files, while pg_restore is used for custom and directory formats. The restoration process requires the target database to be created beforehand. Version mismatches between pg_dump and pg_restore can lead to failures, so it's essential to ensure that the binaries are version-matched. In Docker, pg_dump and pg_restore can be executed within containers, but care must be taken to manage credentials and ensure version compatibility. Exit codes from pg_dump should be checked to confirm successful operations.