Posts

While running an Ansible playbook on one of my servers from an Arch device, I encountered the following error: TASK [Gathering Facts] ***************************************************************************************************************************************************** [ERROR]: Task failed: Failed to connect to the host via ssh: ssh_askpass: exec(/usr/lib/ssh/ssh-askpass): No such file or directory Host key verification failed. It looks like the /usr/lib/ssh/ssh-askpass file doesn’t exit. To find out what package the missing file comes from, we can use pacman -F or pacman --files. ...

By default, the Deployment in Kubernetes retains 10 ReplicaSets [1]. This number can be configured by setting the .spec.revisionHistoryLimit to a desired number. The following is an example on how to retain just 3 old ReplicaSets in my ‘’n8n’’ Deployment. ➜ k get replicasets -n n8n NAME DESIRED CURRENT READY AGE n8n-57c89d6b7d 0 0 0 91d n8n-5f9fb9c459 0 0 0 80d n8n-666b9476f 0 0 0 80d n8n-66cd6bd8c6 1 1 1 74d n8n-6888cc89bd 0 0 0 91d n8n-7466c456f8 0 0 0 91d n8n-74dfd6cb8c 0 0 0 80d n8n-f8f8f6d7b 0 0 0 237d Let set .spec.revisionHistoryLimit to 3: ...

Occasionally, I need to communicate from a podman container to its host, and I keep forgetting how to that. I know I can always google it, but from what had happened earlier today, having a short note to remind myself how this can be easily done is much preferable in my opinion. To communicate between the container and its host, we can just simply use host.containers.internal or host.docker.internal to refer to the host. ...

I’ve been a happy ZFS user for years, appreciating its robustness and features. Yet, in all that time, I’d never had to rename a pool. That changed today. Whether it’s for better organization, a server migration, or just because you’ve had a change of heart about a name, renaming a ZFS pool is a task that might pop up when you least expect it. I needed to rename my pool from anime35 to anime36. I was pleasantly surprised to find the process is incredibly simple and elegant, which is what I’ve come to expect from ZFS. ...

While I was performing an upgrade of Fedora 41 to 42 on my laptop, I noticed there was package installed since Fedora 38. This package, zfs-dkms-2.2.0-1.fc38.noarch, needed to be removed as it blocked this Fedora 42 upgrade. TL;DR - The solution is to use --noscripts option with rpm command. If you want to see how the zfs-dkms package removed, follow along. Here’s the info about the package: root@benjo:/etc/yum.repos.d# dnf info zfs-dkms Updating and loading repositories: Repositories loaded. Installed packages Name : zfs-dkms Epoch : 0 Version : 2.2.0 Release : 1.fc38 Architecture : noarch Installed size : 56.9 MiB Source : zfs-dkms-2.2.0-1.fc38.src.rpm From repository : zfs Summary : Kernel module(s) (dkms) URL : https://github.com/openzfs/zfs License : CDDL Description : This package contains the dkms ZFS kernel modules. Vendor : <NULL> Available packages Name : zfs-dkms Epoch : 0 Version : 2.3.2 Release : 1.fc41 Architecture : noarch Download size : 31.0 MiB Installed size : 58.6 MiB Source : zfs-dkms-2.3.2-1.fc41.src.rpm Repository : zfs Summary : Kernel module(s) (dkms) URL : https://github.com/openzfs/zfs License : CDDL Description : This package contains the dkms ZFS kernel modules. Vendor Let’s try to remove it normally: ...