<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Coreos Ignition Butane on A Random Walk Down Tech Street</title>
    <link>https://dustymabe.com/tags/coreos-ignition-butane/</link>
    <description>Recent content in Coreos Ignition Butane on A Random Walk Down Tech Street</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 12 Aug 2025 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://dustymabe.com/tags/coreos-ignition-butane/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>PoC: Leveraging Butane during Ignition boot</title>
      <link>https://dustymabe.com/2025/08/12/poc-leveraging-butane-during-ignition-boot/</link>
      <pubDate>Tue, 12 Aug 2025 00:00:00 +0000</pubDate>
      <guid>https://dustymabe.com/2025/08/12/poc-leveraging-butane-during-ignition-boot/</guid>
      <description>&lt;h1 id=&#34;converting-butane-to-ignition-on-boot&#34;&gt;Converting Butane to Ignition on Boot&lt;/h1&gt;&#xA;&lt;p&gt;We&amp;rsquo;ve received anecdotal evidence over the years that the&#xA;transpilation step where you must convert a Butane YAML configuration&#xA;into Ignition JSON before staring your CoreOS instance is a pain&#xA;for users to understand and implement. CoreOS developers also feel&#xA;this pain at times.&lt;/p&gt;&#xA;&lt;p&gt;What if you could feed either a Butane YAML config or an Ignition JSON&#xA;config to your instance and it would just do the right thing&#xA;regardless?&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
