You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Proxmox | Fix "e1000e Detected Hardware Unit Hang"
Proxmox network unavailability problems after upgrading to 8.4.1
After upgrading to 8.x, sometimes access to the proxmox lan/web interface/ssh fails to connect after plugging off and on the ethernet port, it works again for some time and this problem occurs again.
When i connected a monitor and keyboard to the proxmox machine,
First i read and thought the new device naming is the problem, so i updated the GRUB_CMDLINE_LINUX field on /etc/default/grub file:
it became like this after adding:
Ollama Web UI(running on WSL Docker) Config With Ollama running on Windows:
I have installed docker on my WSL linux machine, and i have already been using ollama on windows. With these setup in mind i wrote this gist for future reference.
When you run ollama-webui on docker on wsl and your ollama already running on windows machine, webui can not connect to ollama running on windows. For it to work you need to take these steps:
Make Ollama on Windows accessible on network:
Default makes ollama only accessible via localhost(127.0.0.1). To make it accessible on any network devices on the Windows machine, you need to add an environment variable named OLLAMA_HOST with value of 0.0.0.0. Check out the example below:
Add passworddless sudo user via ansible for Ubuntu 22.04 VM's(for personal uses/learning purposes only)
For my learning environment, i needed to quickly and correctly add a passwordless sudo user(for Ubuntu 22.04 VM), since i'm learning ansible, i decided to write the necessary inventory and playbook file, after that i decided to make it customizable via a bash script. User can enter the new user details(name and password) and machine ssh connection information (ip, username and password). And this script first tests the connection via ansible's ping module, after successful operation, asks user to run the generated playbook(or exit and show the command to run the playbook)
These bash scripts:
install python3,pip and sshpass(for ansible), and install ansible via pip
asks user to enter the new user details (username and password) to generate the ansible playbook
asks user to enter the remote machine information to generate the ansible inventory