Ubuntu

I have recently seen lost of AI content from many big companies and have wanted to experiment with it my self. The most practical thing I have been able to think of is an AI assistant on my PC. I started when I saw this video (https://www.youtube.com/watch?v=XvbVePuP7NY&t) from network chuck. This was prity close to what I wanted so I gave it a go. The first issue I ran into was the inability to have add ons when home assistant is installed in docker. However this was a simple fix I just installed them as separate docker containers and manually added them to the whyoming intergration. I then installed the whyoming satalite on my main PC which went smoothly. However I did the extra step of adding sounds to the start and end. ...

It started when I went back to my pterodactyl panel after a long time. I saw a red heart and a invalid ssl cert warning in console. I renewed the cert and the heart went green. However my servers still wern’t loading. So I changed the forwarding from cloudflare to nginx proxy. This still didn’t work. Then I renewed the cert as rsa type and noticed it put it a folder that ended in 00001. So I deleted the one with out the numbers and then renamed the one left to remove the numbers. One restart later and it was all working.

When I revisted my kasm server I found I was unable to launch a session. After running docker ps I saw that the guac container was contantly restarting. After searching the error message I found this link (https://kasmweb.atlassian.net/servicedesk/customer/portal/3/article/8126468) which shows a fix. After following this guide I got it working again. However the same day one of my friends tried to download a game on a steam continer and I don’t know why but the entire vm froze up and I had to hard stop it. When I restarted it I found the config files filled with @ and nothing else. ...

I started with the docker compose file from https://github.com/open-webui/open-webui. I then edited this changing the volumes to mounts on my nas and changing the port. I then installed a range of models some designed for general conversations and others for coding. I then wanted to add tab auto complete to vscode so i used a section of technotim’s guide (https://technotim.live/posts/ai-stack-tutorial/). This worked fine and was all round a simple process. I look forward to trying to customise some of the models.

I wanted to setup a more simple shareable alternative to VMs. Kasm was a great option which I was very excited to try. I began by setting up the normal docker compose with my normal bind mounts. However it kept getting stuck in a loop after accepting the terms. So I had to switch to a full install on a vm. After that I followed the stock install guide and it all went fine. I setup the workspaces I wanted and they installed fine. However the other issue I ran into was when I tried to add ssh to a vm. No matter what I tried it just wouldn’t work so in the end I decided I could just use the Ubuntu workspace and manually ssh in.

This project has been a roll-coaster and one of the hardest things I have attempted my goal when I set out was simple to run local Ollama models on a cheap £60 k80 GPU. My first attempted end very quickly when I found out that the GPU I got was faulty and it spewed out smoke within a second of first boot. After I confirmed the rest of my server was unharmed I got a full refund and purchased another K80. This one did not fail on first boot and so I was able to start setting up my GPU. I spent the next month trying on and off failing every time. ...

I began by trying to install pterodactyl as 2 separate containers on my main docker VM however this ended up having far to many issues for me to try and solve. My next idea was to use the ubuntu container and install them in there however this also didn’t work. In the end i just created a new VM and using this script (https://github.com/pterodactyl-installer/pterodactyl-installer). Which after a bit of fiddling with the ssl record and making the panel and the wing have unique domains then it finally worked. I also made sure that the servers are stored on a nfs share for easy backups. ...

I began by creating a VM and adding a nfs share however my first attempt I installed Docker with the Ubuntu installer this lead to a wide range of problems so justed deleted the VM and started again. On my next attempt I made sure to only install docker after using apt install. I managed to get Portainer to work first try and then just had to move my old containers off my PC, this was not to bad as i just moved the files to the network share and then translated the compose files to the Portainer container options (I later found out that i could do it with docker compose files and switched most of them to that).