<?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 QRL.dev</title>
		<link>https://qrl.dev/categories/docker/</link>
		<description>Recent content in Docker on QRL.dev</description>
		<generator>Hugo</generator>
		<language>en-gb</language>
		
		
		
		
			<lastBuildDate>Sun, 27 Sep 2026 09:00:00 +0000</lastBuildDate>
		
			<atom:link href="https://qrl.dev/categories/docker/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Know what your node is running</title>
				<link>https://qrl.dev/posts/docker-observability/</link>
				<pubDate>Sun, 27 Sep 2026 09:00:00 +0000</pubDate>
				<guid>https://qrl.dev/posts/docker-observability/</guid>
				<description>&lt;p&gt;A running container answers one question: did the process start? It does not tell you which image is running, where its data lives, or whether the application is ready. Those distinctions matter when you are debugging a local node.&lt;/p&gt;&#xA;&lt;p&gt;This note is an inspection checklist for an existing development container. The examples use &lt;code&gt;qrl-node&lt;/code&gt; as its name; replace that with your own. It is not an installation recipe.&lt;/p&gt;&#xA;&lt;h2 id=&#34;start-with-the-image&#34;&gt;Start with the image&lt;/h2&gt;&#xA;&lt;p&gt;Inspect both the configured image reference and the immutable image ID. A tag is convenient, but the image ID helps establish what was actually used on this machine.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
