Windows

Docker Desktop on Windows uses WSL2 with dynamic VHDX files. They grow when adding images/containers but don’t shrink automatically when deleting them. Result: C: drive fills up, even though docker system df shows free space. 💡 Solution: manual VHDX optimization via PowerShell + Docker utility. 📦 Cleanup script Create file # File: $HOME\Scripts\docker-clear-wsl.ps1 $script = @' $LOCAL = "$env:LOCALAPPDATA\Docker\wsl" $VHD1 = Join-Path $LOCAL "disk\docker_data.vhdx" $VHD2 = Join-Path $LOCAL "main\ext4.vhdx" # 1. Docker cleanup docker system prune -f # 2. Reclaim space via official tool docker run --rm --privileged --pid=host docker/desktop-reclaim-space docker rmi docker/desktop-reclaim-space -f # 3. Stop Docker Desktop Get-Process -Name "Docker Desktop","com.docker.backend","com.docker.build" ` -ErrorAction SilentlyContinue | Stop-Process -Force -ErrorAction SilentlyContinue # 4. Shutdown WSL wsl --shutdown # 5. Optimize VHDX files (compact) if (Test-Path $VHD1) { Optimize-VHD -Path $VHD1 -Mode Full } if (Test-Path $VHD2) { Optimize-VHD -Path $VHD2 -Mode Full } # 6. Restart Docker Desktop Start-Sleep -Seconds 2 Start-Process -FilePath "$env:ProgramFiles\Docker\Docker\Docker Desktop.exe" ` -ErrorAction SilentlyContinue '@ $script | Out-File -FilePath "$HOME\Scripts\docker-clear-wsl.ps1" -Encoding UTF8 Run # As Administrator (required for Optimize-VHD) powershell.exe -ExecutionPolicy Bypass -File "$HOME\Scripts\docker-clear-wsl.ps1" 🔍 How it works Step Command What it does 1 docker system prune -f Removes stopped containers, unused images, build cache 2 docker/desktop-reclaim-space Official Docker tool to reclaim space in WSL2 3 Stop-Process Gracefully stops Docker Desktop (otherwise VHDX is locked) 4 wsl --shutdown Fully shuts down WSL, freeing files for optimization 5 Optimize-VHD -Mode Full Compacts VHDX files, returning space to host 6 Start-Process Restarts Docker Desktop Why this way: ...

Git is a version control system. It tracks code changes, enables team collaboration, and lets you undo mistakes. 💡 Install once, use for years. Installation Windows Option 1: Official installer (recommended) Download from git-scm.com Run installer, keep defaults Important: On “Adjusting your PATH” step, select Git from the command line and also from 3rd-party software Option 2: Via Winget (PowerShell) winget install Git.Git Option 3: Via Chocolatey choco install git -y Linux Ubuntu / Debian sudo apt update sudo apt install git -y Fedora / RHEL ...

OpenSSH is a tool for secure remote access via the SSH protocol. It encrypts all traffic, supports key-based authentication, and works on Windows, Linux, and macOS. 💡 After setup, you can connect to your Windows PC like a Linux server: ssh user@192.168.1.100 Requirements OS: Windows 10 (1809+), Windows 11, Windows Server 2019/2022 Privileges: Administrator Network: Access to port 22 (local or remote) Installation (3 ways) Option 1: PowerShell (recommended) # Run as Administrator # Install OpenSSH server Add-WindowsCapability -Online -Name OpenSSH.Server~~~~0.0.1.0 # Verify installation Get-WindowsCapability -Online | Where-Object Name -like 'OpenSSH*' Option 2: DISM (alternative) dism /Online /Add-Capability /CapabilityName:OpenSSH.Server~~~~0.0.1.0 Option 3: Via Settings (GUI) Settings → Apps → Optional features “Add a feature” → find “OpenSSH Server” → Install Configure the service # Run as Administrator # Enable auto-start for sshd Set-Service -Name sshd -StartupType Automatic # Start the service Start-Service sshd # Check status Get-Service sshd # Verify port 22 is listening netstat -ano | findstr :22 Firewall # Check for OpenSSH rule Get-NetFirewallRule -Name *OpenSSH-Server* | Select Name, Enabled # If missing, create it New-NetFirewallRule -Name sshd ` -DisplayName 'OpenSSH Server' ` -Enabled True ` -Direction Inbound ` -Protocol TCP ` -LocalPort 22 ` -Action Allow ` -Profile Any Test connection # From the same PC ssh localhost # From another device on the network ssh <your_username>@<Windows_IP> # Example: ssh kirill@192.168.1.100 💡 First connection will ask to confirm the host key fingerprint - type yes. ...

WSL (Windows Subsystem for Linux) lets you run native Linux command-line tools directly on Windows - no VM, no dual boot. WSL1 - syscall translation layer (fast, but not 100% compatible) WSL2 - real Linux kernel in lightweight virtualization (full compatibility, slightly more resources) 💡 Use WSL2. Near-native performance with full Docker, systemd, and Linux feature support. Requirements OS: Windows 10 (2004+, build 19041+) or Windows 11 Architecture: x64 or ARM64 Privileges: Administrator (for install) Virtualization: Enabled in BIOS/UEFI (Hyper-V Platform) Check virtualization: ...