With Kitty, the top command in SSH shows nothing. I tried htop, but it returned an error.
What I did: Googled the issue and looked for a better solution.
Solution 1: Directly in the SSH terminal session:
TERM=xterm top
Solution 2: Add to local .ssh/config file
SetEnv TERM=xterm
nmcli connection import type openvpn file vpn-config.ovpn
Option 1
cat /sys/class/power_supply/BAT0/capacity
Option 2: install the package acpi and
acpi -i
Sources:
Before my experience as a project manager, I had thought that you knew the details of how to perform a task only if you had implemented it yourself. However, I have discovered another aspect. If you closely participate in the implementation process of a task carried out by someone else—engaging in discussions about progress, problems, taking notes, etc.—you also gain detailed knowledge of how to implement it.
In conclusion, my initial assumption was not the minimal conclusion in terms of the level of detail required. The minimal level is having a good level of communication and involvement in the process.
I have a Redis/Redis Stack container that I would like to start automatically at system boot. Since it is already running, I needed command
docker update --restart=always aa6daa0d965eHowever, if it is starting for the first time, I use command
docker run --restart=always
There is also a third option: transform the container into a service and manage it with systemctl: https://stackoverflow.com/a/39493500/2806801.
There is no host.docker.internal provided by default on Linux. On macOS and Windows, Docker Desktop creates a virtual network bridge and provides host.docker.internal as a hostname to allow containers to communicate with the host system. However, Linux uses a different approach for container networking, so host.docker.internal is not automatically provided.
One solution is to use the host's IP address. Run the command ip addr show docker0 to find the IP address of the Docker bridge network. It is usually 172.17.0.1.
After the last upgrade of Arch Linux using pacman -Syu, PostgreSQL failed to start, displaying an error indicating that the database was in an outdated format. This meant that I had inadvertently upgraded PostgreSQL from one major version to another without first exporting the database as a precaution.
Fortunately, I found this article: How to Downgrade Packages in Arch Linux, and the following steps resolved my problem:
yay -S downgrade
sudo downgrade postgresql
