Siritas S dahoba

Building nginx on Windows (x86 and x64) with additional modules (VS 2022)

These sources were used in compiling this doc:

Permanent WSL DNS Fix (WSL 2.2.1+)

If you're encountering ping github.com failing inside WSL with a Temporary failure in name resolution, you're not alone — this has been a long-standing issue, especially when using VPNs or corporate networks.

This issue is now fixed robustly with DNS tunneling, which preserves dynamic DNS behavior and avoids limitations like WSL’s former hard cap of 3 DNS servers in /etc/resolv.conf.

DNS tunneling is enabled by default in WSL version 2.2.1 and later, meaning that if you're still seeing DNS resolution issues, the first and most effective fix is simply to upgrade WSL. Upgrading WSL updates the WSL platform itself, but does not affect your installed Linux distributions, apps, or files.

To upgrade WSL, follow these steps,

UPDATE (March 2020, thanks @ic): I don't know the exact AMI version but yum install docker now works on the latest Amazon Linux 2. The instructions below may still be relevant depending on the vintage AMI you are using.

Amazon changed the install in Linux 2. One no-longer using 'yum' See: https://aws.amazon.com/amazon-linux-2/release-notes/

Docker CE Install

sudo amazon-linux-extras install docker
sudo service docker start

Get load balancer ARN

arn=$(aws elbv2 describe-load-balancers --names <value> --query 'LoadBalancers[].[LoadBalancerArn]' --output text)

Get listeners

aws elbv2 describe-listeners --load-balancer-arn "$arn" --query 'Listeners[].{ListenerArn:ListenerArn,Protocol:Protocol,Port:Port}'

	#!/bin/bash

	# Script that updates the iTerm Badge with the hostname of the server that you are
	# connecting to with ssh.
	#
	# Instructions:
	# - Put this script in ~/bin/ssh (this will override the default ssh binary)
	# - Run 'chmod +x ~/bin/ssh' to give execution permission to the script
	# - Open iTerm\Preferences\Profiles, select your profile and put '\(user.current_ssh_host)' in the Badge text box
	# - Enjoy!

	# non root user example for alpine
	#
	# usage:
	# $ docker build --build-arg "USER=someuser" --tag test .
	# $ docker run --rm test

	FROM alpine

	ARG USER=default
	ENV HOME /home/$USER

	#!/bin/sh
	# OUTDATED: please refer to the link below for the latest version:
	# https://github.com/rancherlabs/support-tools/blob/master/extended-rancher-2-cleanup/extended-cleanup-rancher2.sh
	docker rm -f $(docker ps -qa)
	docker volume rm $(docker volume ls -q)
	cleanupdirs="/var/lib/etcd /etc/kubernetes /etc/cni /opt/cni /var/lib/cni /var/run/calico /opt/rke"
	for dir in $cleanupdirs; do
	echo "Removing $dir"
	rm -rf $dir
	done

	#!/bin/bash
	# =============================================================================
	# Author: Chu-Siang Lai / chusiang (at) drx.tw
	# Filename: teams-chat-post-for-workflows.sh
	# Modified: 2024-07-22 11:44 (UTC+08:00)
	# Description: Post a message to Microsoft Teams via "Post to a chat when a webhook request is received" workflows.
	# Reference:
	#
	# - https://gist.github.com/chusiang/895f6406fbf9285c58ad0a3ace13d025
	# - https://devblogs.microsoft.com/microsoft365dev/retirement-of-office-365-connectors-within-microsoft-teams/

	$userPath = $env:USERPROFILE
	$pathExclusions = New-Object System.Collections.ArrayList
	$processExclusions = New-Object System.Collections.ArrayList

	$pathExclusions.Add('C:\Windows\Microsoft.NET') > $null
	$pathExclusions.Add('C:\Windows\assembly') > $null
	$pathExclusions.Add($userPath + '\AppData\Local\Microsoft\VisualStudio') > $null
	$pathExclusions.Add('C:\ProgramData\Microsoft\VisualStudio\Packages') > $null
	$pathExclusions.Add('C:\Program Files (x86)\MSBuild') > $null
	$pathExclusions.Add('C:\Program Files (x86)\Microsoft Visual Studio 14.0') > $null

Siritas S dahoba

Building nginx on Windows (x86 and x64) with additional modules (VS 2022)

Table of contents

Steps:

Permanent WSL DNS Fix (WSL 2.2.1+)

Docker CE Install