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....
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....
When running argocd CLI, the following warning message shown: ➜ argocd app list WARN[0000] Failed to invoke grpc call. Use flag --grpc-web in grpc calls. To avoid this warning message, use flag --grpc-web. NAME CLUSTER NAMESPACE PROJECT STATUS HEALTH SYNCPOLICY CONDITIONS REPO PATH TARGET To suppress this warning message, re-run the login with --grpc-web option. For example: ➜ argocd login argocd.apps.tuaf.local.cluster --grpc-web Username: admin Password: 'admin:login' logged in successfully Context 'argocd....
I want to reset a file stored in a git repo to its state as the main branch, and I kept forgetting how to do this. So here is how, just to remind my future self. ➜ git status On branch main Your branch is up to date with 'origin/main'. Changes not staged for commit: (use "git add <file>..." to update what will be committed) (use "git restore <file>..." to discard changes in working directory) modified: kube-prometheus-stack-values....
When deploying the prometheus-community/kube-prometheus-stack in a k8s cluster, the default retention for Prometheus scrapped data is 10d at the time of this writing or Helm chart kube-prometheus-stack-69.4.1. As a result, the longhorn storage is filled up fast, and caused the Prometheus to crash. So I’d decided to change the retention period to 3 days, and also set retention size to 4GB. To do this, update the values file for the Helm chart with the following values:...
This is a quick note on how to reset the password of user account on the open sourced Xen Orchestra. To reset the password of a user, of course, you’d need to know the user account, e.g. admin@admin.net. [root@xoa1 xo-server]# cd /opt/xo/xo-server [root@xoa1 xo-server]# ./dist/recover-account-cli.mjs --help xo-server-recover-account <user name or email> If the user does not exist, it is created, if it exists, updates its password, remove any configured OTP and resets its permission to Admin....
Up until recently, my preferred method of creating Podman containers is to use Ansible, and that has been working fine for me. However, I just stumble the new-to-me method called “quadlet”. So far, I really like it, and already started moving some containers to quadlet. To learn more about Quadlet, check out [1]. But, today I’m going to share an example of creating a simple container with Quadlet. In this example, the container whoami is run in rootless mode, under a non-privileged user....
If you use ZFS as the file system, you probably already know that tank is the most common name for ZFS pools. That also applies to me, I do name most of my ZFS pools as tank as the default. There is no issue with that name, however, since ZFS’s pool name must be unique, this means I couldn’t import or have multiple ZFS pools with the name tank on a system....
“The systemd login manager will terminate any user services when their login session ends unless you enable user lingering with the enable-linger option. Use loginctl with the enable-linger option to configure a user to start during the boot process and prevent the systemd service from terminating when the user session ends.” [1] To enable linger for a user, e.g. kenno, we can run the following command: # loginctl enable-linger kenno I usually ran the above command, and that was it....
Sometimes you need to connect to the host from a Podman container running on it. How would you do that? In the past I was able to get this working by connecting to the gateway IP of the container. For example, I have a web server running on the host listening on port 8080. ➜ nc -vz localhost 8080 Ncat: Version 7.92 ( https://nmap.org/ncat ) Ncat: Connected to 127.0.0.1:8080. Ncat: 0 bytes sent, 0 bytes received in 0....