<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Uncloud on Miek Gieben</title>
    <link>https://miek.nl/tags/uncloud/</link>
    <description>Recent content in Uncloud on Miek Gieben</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <copyright>© Copyright 2007-2024 Miek Gieben</copyright>
    <lastBuildDate>Sun, 26 Apr 2026 18:22:52 +0200</lastBuildDate>
    <atom:link href="https://miek.nl/tags/uncloud/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Uncloud Prometheus</title>
      <link>https://miek.nl/2026/april/26/uncloud-prometheus/</link>
      <pubDate>Sun, 26 Apr 2026 18:22:52 +0200</pubDate>
      <guid>https://miek.nl/2026/april/26/uncloud-prometheus/</guid>
      <description>&lt;p&gt;&lt;a href=&#34;https://github.com/psviderski/uncloud/pull/304&#34;&gt;Prometheus metrics&lt;/a&gt; are being worked on by&#xA;&lt;a href=&#34;https://ratms.nl/projects/uncloud/&#34;&gt;me&lt;/a&gt;, and will hopefully soon be merged in &lt;a href=&#34;https://uncloud.run&#34;&gt;Uncloud&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;p&gt;The &lt;em&gt;uncloudd&lt;/em&gt; metrics endpoint is exposed into the cluster network, so this makes it possible for a&#xA;Prometheus service running inside the cluster to scrape it. For this it just needs to be able to access the API&#xA;to get all machines in the cluster. This can be done by mounting the uncloud socket inside the container, and&#xA;using &lt;code&gt;uc&lt;/code&gt; with &lt;a href=&#34;https://github.com/psviderski/uncloud/issues/335&#34;&gt;structured output&lt;/a&gt;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Uncloud L4</title>
      <link>https://miek.nl/2026/april/25/uncloud-l4/</link>
      <pubDate>Sat, 25 Apr 2026 13:21:52 +0200</pubDate>
      <guid>https://miek.nl/2026/april/25/uncloud-l4/</guid>
      <description>&lt;p&gt;Natively &lt;a href=&#34;https://uncloud.run&#34;&gt;Uncloud&lt;/a&gt; doesn&amp;rsquo;t do L4 forwarding. This is an &lt;a href=&#34;https://github.com/psviderski/uncloud/issues/108&#34;&gt;open&#xA;issue&lt;/a&gt; as we are figuring out how to actually do this. But&#xA;it turns out you can already do this with the current code - well almost.&lt;/p&gt;&#xA;&lt;p&gt;Buckle up, because there is quite some stuff you may need:&lt;/p&gt;&#xA;&lt;ol&gt;&#xA;&lt;li&gt;A patched Uncloud, see &lt;a href=&#34;https://github.com/psviderski/uncloud/pull/358&#34;&gt;this PR&lt;/a&gt; for that.&lt;/li&gt;&#xA;&lt;li&gt;A custom &lt;a href=&#34;https://caddyserver.com&#34;&gt;Caddy&lt;/a&gt; build, with the &lt;a href=&#34;https://github.com/mholt/caddy-l4&#34;&gt;L4&lt;/a&gt; plugin.&lt;/li&gt;&#xA;&lt;li&gt;A DNS server, I use &lt;a href=&#34;https://atomdns.miek.nl&#34;&gt;atomdns&lt;/a&gt; of course.&lt;/li&gt;&#xA;&lt;/ol&gt;&#xA;&lt;h1 id=&#34;caddy&#34;&gt;Caddy&lt;/h1&gt;&#xA;&lt;p&gt;With the following Dockerfile you create a custom caddy image that we will use.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Uncloud Private Registries</title>
      <link>https://miek.nl/2026/april/14/uncloud-private-registries/</link>
      <pubDate>Tue, 14 Apr 2026 19:31:00 +0200</pubDate>
      <guid>https://miek.nl/2026/april/14/uncloud-private-registries/</guid>
      <description>&lt;p&gt;While pushing &lt;a href=&#34;https://github.com/psviderski/uncloud/pull/306&#34;&gt;this PR&lt;/a&gt;, the answer was that this &lt;em&gt;was already&#xA;working&lt;/em&gt;! But kind of unintuitive, but smart as it re-uses whatever docker setup you got (i.e. credentials&#xA;helpers).&lt;/p&gt;&#xA;&lt;p&gt;So to get this working you:&lt;/p&gt;&#xA;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; style=&#34;color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;&#34;&gt;&lt;code class=&#34;language-sh&#34; data-lang=&#34;sh&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;% docker login registry.science.ru.nl&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;Username: bla&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;Password:&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;...&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;And then use &lt;code&gt;uc deploy -f .../compose.yml&lt;/code&gt; just like you did before. Now it should pull from the private repo&#xA;and things &amp;ldquo;just work&amp;rdquo;.&lt;/p&gt;&#xA;&lt;p&gt;See &lt;a href=&#34;https://uncloud.run/docs/guides/deployments/deploy-app/#pull-from-a-private-registry&#34;&gt;this guide&lt;/a&gt; for&#xA;canonical text on this.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Uncloud</title>
      <link>https://miek.nl/2026/march/16/uncloud/</link>
      <pubDate>Mon, 16 Mar 2026 14:00:40 +0100</pubDate>
      <guid>https://miek.nl/2026/march/16/uncloud/</guid>
      <description>&lt;p&gt;I&amp;rsquo;m playing with &lt;a href=&#34;https://uncloud.run&#34;&gt;Uncloud&lt;/a&gt; to see if it is something we can use at $WORK. Pretty&#xA;impressed with it already, as I&amp;rsquo;ve written something worse &lt;a href=&#34;https://github.com/miekg/pgo&#34;&gt;pgo&lt;/a&gt;, that was&#xA;(obviously) not good enough. Uncloud does: implement a subset of the Docker(-compose) API, uses gRPC and&#xA;wireguard to create mini network; just brilliant. Haven&amp;rsquo;t seen prometheus metrics yet, although Caddy is used&#xA;for the proxy, but more prometheus metrics would make sense. (Which you can then observe through a cluster&#xA;hosted prometheus&amp;hellip;?)&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
