<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Kasm on Keldo.uk</title>
    <link>https://keldo.uk/tags/kasm/</link>
    <description>Recent content in Kasm on Keldo.uk</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Thu, 01 Aug 2024 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://keldo.uk/tags/kasm/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Kasm storage complications</title>
      <link>https://keldo.uk/server/proxmox/vms/kasm/kasm-storage-complications/</link>
      <pubDate>Thu, 01 Aug 2024 00:00:00 +0000</pubDate>
      <guid>https://keldo.uk/server/proxmox/vms/kasm/kasm-storage-complications/</guid>
      <description>&lt;p&gt;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 (&lt;a href=&#34;https://kasmweb.atlassian.net/servicedesk/customer/portal/3/article/8126468&#34;&gt;https://kasmweb.atlassian.net/servicedesk/customer/portal/3/article/8126468&lt;/a&gt;) which shows a fix. After following this guide I got it working again.&lt;/p&gt;
&lt;p&gt;However the same day one of my friends tried to download a game on a steam continer and I don&amp;rsquo;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.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Kasm install</title>
      <link>https://keldo.uk/server/proxmox/vms/kasm/kasm-install/</link>
      <pubDate>Sat, 11 May 2024 00:00:00 +0000</pubDate>
      <guid>https://keldo.uk/server/proxmox/vms/kasm/kasm-install/</guid>
      <description>&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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&amp;rsquo;t work so in the end I decided I could just use the Ubuntu workspace and manually ssh in.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
