| ### Run this script on Windows (outside of the devcontainer!) to clear out Docker data and shrink the Docker VHD. | |
| # Check if running as administrator, if not, relaunch as admin | |
| if (-NOT ([Security.Principal.WindowsPrincipal] [Security.Principal.WindowsIdentity]::GetCurrent()).IsInRole([Security.Principal.WindowsBuiltInRole] "Administrator")) { | |
| Write-Host "Script requires administrator privileges. Relaunching as administrator..." -ForegroundColor Yellow | |
| # Get the current script path | |
| $scriptPath = $MyInvocation.MyCommand.Path | |
| # Relaunch the script as administrator |
Previous tutorials didnt worked for me because my setup is a little bit odd.
I'm using windows 11 machine with WSL2 and docker desktop.
I also use k3d to create kubernetes cluster. Also my k3d cluster have local registry
I also used skaffold and other shinigens
%USERPROFILE%\AppData\Local\Docker\wsl\disk\ - there is your docker_data.vhdx
| #!/bin/bash | |
| # Strict mode: exit on error, exit on unset variable, pipefail | |
| set -euo pipefail | |
| echo "🚀 Installing Distrobox on macOS with full Podman support..." | |
| # 1. Check for Homebrew | |
| if ! command -v brew >/dev/null 2>&1; then | |
| echo "❌ Homebrew is not installed. Please install it first: https://brew.sh" |
| # Virtual memory settings. | |
| # Kernel documentation: https://docs.kernel.org/admin-guide/sysctl/vm.html. | |
| # Arch zram: https://wiki.archlinux.org/title/zram#Optimizing_swap_on_zram. | |
| # Gaming tuning: https://pastebin.com/fwzW9whL. | |
| # PopOS tuning: https://github.com/pop-os/default-settings/pull/163. | |
| # MaxPerformanceWizard (MPW) https://gitlab.com/cscs/maxperfwiz/-/blob/master/maxperfwiz. | |
| boot.kernel.sysctl = { | |
| # Tunes how aggressively kernel evicts memory pages until a specific amount of free memory is left for your active working set | |
| ## Sweet spot for gaming is 125-200, near 200 makes kswapd swap too aggressive |
My tutorial is based on this one from pudquick
If you encounter a problem where you cannot commit changes in Git – neither through the terminal nor via the GitHub Desktop application – the issue might be a freeze during the Git commit process. This is often caused by GPG lock issues. Below is a concise and step-by-step guide to resolve this problem.
Open your terminal and try to perform a GPG operation (like signing a test message). If you see repeated messages like gpg: waiting for lock (held by [process_id]) ..., it indicates a lock issue.
| #!/bin/sh | |
| cage -- bash -c 'wlr-randr --output X11-1 --custom-mode 1280x800; sleep 1; sudo /usr/local/bin/waydroid-helper & waydroid show-full-ui' |
