Posts

I’m installing minikube on my shiny new Pop!OS 20.10 install which is based on Ubuntu 20.10. >_lsb_release -a No LSB modules are available. Distributor ID: Pop Description: Pop!_OS 20.10 Release: 20.10 Codename: groovy I prefer to have my standalone application binaries placed in ~/.bin/ which is already included in my PATH. >_ cd ~/.bin >_ curl -LO https://storage.googleapis.com/minikube/releases/latest/minikube-linux-amd64 % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 53....

Problem Some of my docker containers access resources from a NAS over NFS. On reboot, the Docker service comes up before the NFS paths are mounted, this causes the services within my containers to fail. Restating the docker service, systemctl restart docker fixes this but I’d rather the containers come up properly the first time. Solution Add a systemd drop-in unit for the docker service instructing it to wait for the NFS mount to come online before starting....

My Arch update broke today with the following error which was due to a missing soname entry in the older nss packages. The error was identified and a post describing the error with a fix was posted to the ArchLinux news feed. Read Here ? sudo pacman -Syu ..... ..... (201/201) checking for file conflicts [------------------------------------------------------------] 100% error: failed to commit transaction (conflicting files) nss: /usr/lib/p11-kit-trust.so exists in filesystem lib32-nss: /usr/lib32/p11-kit-trust....

I used the change shell command chsh to change the default shell environment for my id from BASH to the FISH shell. >_ chsh Changing shell for danesh.manoharan. New shell [/bin/bash]: /usr/bin/fish Password: Shell changed. >_ chsh -s /usr/bin/fish Changing shell for danesh.manoharan. chsh: Shell changed.

I recently purchased a thunderbolt 3 to 10GbE adapter ( QNA-T310G1S ) for my homelab NUC ( NUC7i5BNH ) running Fedora server 30. The network interface was not showing up when I connected the adapter. Some googling later and I figured out what I was not doing. Thunderbolt devices need to be authorized and added to the thunderbolt device manager before they can be used. This requirement can be changed in the BIOS if desired....