<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Docker on rikosjett</title><link>https://rikosjett.com/topics/docker/</link><description>Recent content in Docker on rikosjett</description><generator>Hugo</generator><language>en</language><lastBuildDate>Tue, 31 Mar 2026 00:00:00 +0200</lastBuildDate><atom:link href="https://rikosjett.com/topics/docker/index.xml" rel="self" type="application/rss+xml"/><item><title>Install Colima and configure Docker CLI plugins</title><link>https://rikosjett.com/til/43/</link><pubDate>Tue, 31 Mar 2026 00:00:00 +0200</pubDate><guid>https://rikosjett.com/til/43/</guid><description>&lt;h2 id="install-colima"&gt;Install colima&lt;/h2&gt;
&lt;p&gt;brew install colima&lt;/p&gt;
&lt;h2 id="install-docker-client-and-docker-compose"&gt;Install docker client and docker compose&lt;/h2&gt;
&lt;p&gt;brew install docker docker-compose&lt;/p&gt;
&lt;h2 id="configure-plugin"&gt;Configure plugin&lt;/h2&gt;
&lt;p&gt;For Docker to find the plugin, add &amp;quot;cliPluginsExtraDirs&amp;quot; to ~/.docker/config.json:
&amp;quot;cliPluginsExtraDirs&amp;quot;: [
&amp;quot;/opt/homebrew/lib/docker/cli-plugins&amp;quot;
]&lt;/p&gt;</description></item><item><title>Exposing Immich over Tailscale with a companion container</title><link>https://rikosjett.com/blog/exposing-immich-over-tailscale-with-a-companion-container/</link><pubDate>Sat, 07 Mar 2026 00:00:00 +0100</pubDate><guid>https://rikosjett.com/blog/exposing-immich-over-tailscale-with-a-companion-container/</guid><description>&lt;p&gt;I already had &lt;a href="https://immich.app"&gt;Immich&lt;/a&gt; running on a &lt;a href="https://docs.immich.app/install/synology/"&gt;Synology NAS&lt;/a&gt;, with the &lt;a href="https://tailscale.com"&gt;Tailscale&lt;/a&gt; package installed on the NAS itself. Accessing Immich meant hitting the NAS IP and port. It's functional, but not great. I wanted a proper subdomain, HTTPS, and no port in the URL.&lt;/p&gt;
&lt;p&gt;My idea was to run a Tailscale container alongside Immich, use &lt;code&gt;ts serve&lt;/code&gt; to terminate HTTPS and proxy traffic, and not touch the existing Immich setup at all.&lt;/p&gt;
&lt;h3 id="the-tailscale-container"&gt;The Tailscale container&lt;/h3&gt;
&lt;p&gt;Create a new directory for the stack, e.g. &lt;code&gt;/volume1/docker/IMMICH-TAILSCALE/&lt;/code&gt;, and create the sub-directories &lt;code&gt;state&lt;/code&gt; and &lt;code&gt;config&lt;/code&gt;. You should also prepare some files on your computer, that you will upload before running the stack.&lt;/p&gt;</description></item><item><title>Manage multiple Docker instances using Portainer agent</title><link>https://rikosjett.com/til/8/</link><pubDate>Fri, 26 Mar 2021 00:00:00 +0100</pubDate><guid>https://rikosjett.com/til/8/</guid><description>&lt;h2 id="run-instance-of-portainer-agent-on-docker-instance"&gt;Run instance of portainer agent on docker instance&lt;/h2&gt;

&lt;figure class="code-block"&gt;
 &lt;figcaption&gt;SH&lt;/figcaption&gt;
 &lt;div class="highlight"&gt;&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;"&gt;&lt;code class="language-sh" data-lang="sh"&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;docker run -d -p 9001:9001 --name portainer_agent --restart&lt;span style="color:#f92672"&gt;=&lt;/span&gt;always -v /var/run/docker.sock:/var/run/docker.sock -v /var/lib/docker/volumes:/var/lib/docker/volumes portainer/agent&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;
&lt;/figure&gt;
&lt;h2 id="configure-endpoint-in-portainer-on-management-instance"&gt;Configure endpoint in Portainer on management instance&lt;/h2&gt;

&lt;img src="112557327-850d0580-8dcc-11eb-890d-f2aefe8171da.jpg" alt="agent-endpoint" loading="lazy"&gt;</description></item></channel></rss>