Switching from Docker Desktop to Rancher Desktop on WSL2: Solving the Missing docker-credential-desktop.exe Error I’ve been happily running Kamal inside WSL2 on my home Windows desktop for a while. My original setup included an older Docker Desktop installation. Recently, I wanted to replicate this environment on a different machine, but I discovered that Docker Desktop had changed their licensing terms. Technically, I’m still covered by the new licensing terms, but I decided to try Rancher Desktop instead. Installing Rancher Desktop on WSL2 Installation was straightforward. I installed Rancher Desktop, configured it to integrate with WSL2, and disabled Kubernetes (since I don’t currently need it). My plan was to continue using the Docker CLI inside WSL2 alongside Rancher Desktop for container management. The Authentication Error However, when I was in WSL and tried to authenticate (for example, with Docker Hub via docker login), I ran into this error: ``` failed to store...
A few times I've needed to communicate via VNC, for instance when I was changing network configuration and couldn't use SSH or when I tried out Windows. Communicating with VNC to Proxmox wasn't so easy for me as it seemed in the documentation. Basically I never really got the " /etc/inetd.conf " thing to work, but this made it work from my local machine. This blog post is an alternative to the openbsd-inetd solution In the following: 2.2.2.2 is the IP of my Proxmox host 100 is the VM-ID you picked when you created the virtual machine ======================================================================== ssh -f -L 25901:127.0.0.1:5910 root@ 2.2.2.2 'nc -l -p 5910 -c "qm vncproxy 100 "'; "/Applications/TigerVNC Viewer 1.2.0.app/Contents/MacOS/TigerVNC Viewer" localhost:25901 ======================================================================== Please note that I only got TigerVNC to work, since all the other VNCs ha...
Many Windows users prefer to limit their searches to local files and programs without including internet results. Here's a simple guide to disable Bing search in Windows: ## Step-by-Step Guide 1. Open the Registry Editor - Press `Win + R` to open the Run dialog - Type `regedit` and press Enter 2. Navigate to the following path: `HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Search` 3. Create a new DWORD value: - Right-click in the right panel - Select New > DWORD Value (32-bit) - Name the new value "BingSearchEnabled" 4. Configure the new value: - Double-click on "BingSearchEnabled" - Set the value to 0 5. Restart your computer ## What does this do? By setting "BingSearchEnabled" to 0, you're telling Windows that you don't want to use Bing search in the Windows search function. This limits the search to only include local files and programs.
Comments
Post a Comment