<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Dobbo</title>
		<link>https://www.dobbo.ca/</link>
		<description>Recent content on Dobbo</description>
		<generator>Hugo</generator>
		<language>en</language>
		
		
		
		
			<lastBuildDate>Fri, 18 Sep 2026 09:15:00 -0700</lastBuildDate>
		
			<atom:link href="https://www.dobbo.ca/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Modded Valheim on an Apple Silicon Mac</title>
				<link>https://www.dobbo.ca/posts/valheim/apple-silicon-bepinex/</link>
				<pubDate>Fri, 18 Sep 2026 09:15:00 -0700</pubDate>
				<guid>https://www.dobbo.ca/posts/valheim/apple-silicon-bepinex/</guid>
				<description>&lt;h2 id=&#34;the-problem&#34;&gt;&#xA;  The problem&#xA;  &lt;a class=&#34;heading-link&#34; href=&#34;#the-problem&#34;&gt;&#xA;    &lt;i class=&#34;fa-solid fa-link&#34; aria-hidden=&#34;true&#34; title=&#34;Link to heading&#34;&gt;&lt;/i&gt;&#xA;    &lt;span class=&#34;sr-only&#34;&gt;Link to heading&lt;/span&gt;&#xA;  &lt;/a&gt;&#xA;&lt;/h2&gt;&#xA;&lt;p&gt;Valheim ships a universal macOS build, so it runs natively on Apple Silicon. BepInEx 5 ships a&#xA;universal macOS build too. Put them together and you get a game that launches, plays fine, and&#xA;loads exactly zero plugins.&lt;/p&gt;&#xA;&lt;p&gt;There is no error. There is no &lt;code&gt;BepInEx/LogOutput.log&lt;/code&gt;. There is nothing in &lt;code&gt;Player.log&lt;/code&gt; and&#xA;nothing on stdout. The game behaves as though BepInEx were never installed, which is what makes&#xA;this expensive to debug — every obvious suspect looks innocent because nothing ever complains.&lt;/p&gt;</description>
			</item>
			<item>
				<title>AWS EKS / Node Allocatable Settings</title>
				<link>https://www.dobbo.ca/posts/aws/eks/node_allocatable_settings/</link>
				<pubDate>Fri, 25 Jul 2025 10:33:39 -0700</pubDate>
				<guid>https://www.dobbo.ca/posts/aws/eks/node_allocatable_settings/</guid>
				<description>&lt;h2 id=&#34;details&#34;&gt;&#xA;  Details&#xA;  &lt;a class=&#34;heading-link&#34; href=&#34;#details&#34;&gt;&#xA;    &lt;i class=&#34;fa-solid fa-link&#34; aria-hidden=&#34;true&#34; title=&#34;Link to heading&#34;&gt;&lt;/i&gt;&#xA;    &lt;span class=&#34;sr-only&#34;&gt;Link to heading&lt;/span&gt;&#xA;  &lt;/a&gt;&#xA;&lt;/h2&gt;&#xA;&lt;p&gt;If you’re viewing this page, you’ve likely found that your node is transitioning to “Unknown” status because you cannot apply resource limits to a workload for some reason. You may be seeking a way to protect the kubelet process from being overwhelmed by other workloads in the same cgroup.&lt;/p&gt;&#xA;&lt;h2 id=&#34;protecting-the-kubelet&#34;&gt;&#xA;  Protecting the Kubelet&#xA;  &lt;a class=&#34;heading-link&#34; href=&#34;#protecting-the-kubelet&#34;&gt;&#xA;    &lt;i class=&#34;fa-solid fa-link&#34; aria-hidden=&#34;true&#34; title=&#34;Link to heading&#34;&gt;&lt;/i&gt;&#xA;    &lt;span class=&#34;sr-only&#34;&gt;Link to heading&lt;/span&gt;&#xA;  &lt;/a&gt;&#xA;&lt;/h2&gt;&#xA;&lt;h3 id=&#34;using-kubelet-arguments&#34;&gt;&#xA;  Using Kubelet Arguments&#xA;  &lt;a class=&#34;heading-link&#34; href=&#34;#using-kubelet-arguments&#34;&gt;&#xA;    &lt;i class=&#34;fa-solid fa-link&#34; aria-hidden=&#34;true&#34; title=&#34;Link to heading&#34;&gt;&lt;/i&gt;&#xA;    &lt;span class=&#34;sr-only&#34;&gt;Link to heading&lt;/span&gt;&#xA;  &lt;/a&gt;&#xA;&lt;/h3&gt;&#xA;&lt;p&gt;You can achieve this with minimal configuration by simply adding the following two arguments:&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
