The other day I was playing around in WSL with a colleague of mine and we did this:
[Read More]Windows Subsystem For Linux 2: Debian+Podman
The problem: Docker itself can’t be run in WSL2 as it requires the docker daemon, usually run though systemd.
The solution: Podman works just fine and can easily be installed, although we will need to configure some things to make it work properly.
[Read More]Going Part Time
(Re)starting my indie journey
Simple HTTP Status Monitor Using Curl
yamllint: Ignore exisiting errors
When adding yamllint to an existing project it can be hard to fix all the errors at once.
I wrote a simple script to create a rules block that simply ignores all rules that currently trigger for a file. This works by generating a rules block ignoring paths.
[Read More]Local User Management Polyfill
Older Versions of Windows 10 and all Windows Server 2012 systems have no local user management commandlets.
This is a working polyfill to allow scripts using local user management to run on old systems.
Local S3 with MinIO in Django
Hidden WSL Fileshare
WSL file systems get exposed as a hidden share network share:
\\wsl$\<WSL Name>\<path\to\file>
For example, my Debian home folder is at: \\wsl$\Debian\home\kamner
Windows Terminal: Open New WSL Tab In Linux Home Folder
Resolve .local Through Nameserver With Netplan
When using netplan it is easy to force .local DNS requests to go to you nameservers instead of being only resolved locally (the default and standard).
This also works with all other strange .WHATEVER domains you may have lying around in your organization.
Snippet from netplan configuration:
nameservers:
addresses:
- X
- Y
search:
- local
- myotherstupiddomain
MongoDB Logrotate
Show all active user cron jobs on a system
Debian/Ubuntu
grep -vH "#" /var/spool/cron/crontabs/*
RedHat/Centos/Rocky
grep -vH "#" /var/spool/cron/*
Customize Freshervice User Portal
DNS Resolution Everywhere
Publish Parts Of Obsidian To My Personal Site
curl: Modify DNS Resolution
How SELinux screws with scripts when run over VMware Tools
SELinux by default prohibits certain things from working through VMware tools (Ansible connection or plain API).
This can be solved two ways:
- Disabling SELinux: BAD, but easy
- Writing a custom SELinux policy: complicated but more secure
Note: Adding/Changing this policy through a VMware tools connection is thankfully possible
Example policy
This policy is the base for a VMware tools policy and allows entering the rpm context (yum).
module custom-vmtools 1.0;
require {
type rpm_script_t;
type vmtools_unconfined_t;
class process transition;
}
#============= vmtools_unconfined_t ==============
allow vmtools_unconfined_t rpm_script_t:process transition