Posts

alma linux: dnf Module yaml error: Unexpected key in data

While applying recent updates to a server running Rocky Linux 8, an error presented itself. Module yaml error: Unexpected key in data: static_context [line 9 col 3] Module yaml error: Unexpected key in data: static_context [line 9 col 3] The solution turned out to be a simple one. Update the libmodulemd first to correct the problem then perform the dnf updates as usual. dnf update libmodulemd For a detailed explanation as to the cause of this problem.

Enable UEFI in your VMWare machine

Image
VMWare Workstation 8, 9, and 10 support booting to a UEFI environment. Create a new virtual machine Open the .VMX file of your virtual machine in Notepad (or similar) and add the following line to it: firmware="efi" Save the .VMX file.         In addition, order to be able to select network boot, it is advisable to add a boot delay to the startup of the virtual machine. This can be done by adding the line "bios.bootdelay = 5000" (time is in milliseconds)

Provisions a Ubuntu 20.04 VM in QEMU on Mac OSX using Cloud-Init

#!/usr/bin/env bash #Install brew and qemu + cloud init metadata dependencies /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install.sh )" brew install qemu brew install cdrtools rm -rf /tmp/ubuntuqemuboot #download Ubuntu 20.04 Cloud Image and resize to 30 Gigs mkdir -p /tmp/ubuntuqemuboot/images cd /tmp/ubuntuqemuboot/images curl https://cloud-images.ubuntu.com/focal/current/focal-server-cloudimg-amd64.img --output focal-server-cloudimg-amd64.img qemu-img resize focal-server-cloudimg-amd64.img 30G #create the cloud-init NoCloud metadata disk file mkdir -p /tmp/ubuntuqemuboot/cloudinitmetadata cd /tmp/ubuntuqemuboot/cloudinitmetadata ssh-keygen -b 2048 -t rsa -f id_rsa_ubuntu2004boot -P "" chmod 0600 /tmp/ubuntuqemuboot/cloudinitmetadata/id_rsa_ubuntu2004boot PUBLIC_KEY=$(cat id_rsa_ubuntu2004boot.pub) cat <<EOF >/tmp/ubuntuqemuboot/cloudinitmetadata/meta-data instance-id: circle-the-wagons-local716 local-hostname: ci...

How to import a pfx using certutil without prompt?

Open the powershell as administrator certutil -f -user -p PASSWORD -importpfx c:\cert.pfx NoRoot

K8s registry mirror

https://github.com/spegel-org/spegel

error jailing process inside rootfs: pivot_root .: permission denied: unknown

Error:  Starting keycloak_postgres_1 ... error ERROR: for keycloak_postgres_1  Cannot start service postgres: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error jailing process inside rootfs: pivot_root .: permission denied: unknown ERROR: for postgres  Cannot start service postgres: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error jailing process inside rootfs: pivot_root .: permission denied: unknown ERROR: Encountered errors while bringing up the project. Solution # ln -s /etc/apparmor.d/runc /etc/apparmor.d/disable/ # apparmor_parser -R  /etc/apparmor.d/runc Rebooting the instance might also achieve the same.

Remote kubectl x509: certificate is valid for 127.0.0.1

E0829 10:19:51.734979   13883 memcache.go:265] couldn't get current server API group list: Get "https://x.x.x.x:6443/api? Unable to connect to the server: tls: failed to verify certificate: x509: certificate is valid for 10.43.0.1, 127.0.0.1, 172.31.4.10, ::1, not 13.126.42.175 Solution: edit /etc/systemd/system/k3s.service ExecStart=/usr/local/bin/k3s \    server \       '–advertise-address=106.xx.xx.xx' \       '-tls-san=106.xx.xx.xx' \  ## this is important and kubectl -n kube-system delete secrets/k3s-serving mv /var/lib/rancher/k3s/server/tls/dynamic-cert.json /tmp/dynamic-cert.json systemctl restart k3s