<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Rpm-Ostree on *scratch*</title>
    <link>https://www.scrivano.org/tags/rpm-ostree/</link>
    <description>Recent content in Rpm-Ostree on *scratch*</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Sat, 06 Jun 2026 10:03:54 +0000</lastBuildDate>
    <atom:link href="https://www.scrivano.org/tags/rpm-ostree/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Ostree-docker-builder</title>
      <link>https://www.scrivano.org/2015/09/30/ostree-docker-builder/</link>
      <pubDate>Wed, 30 Sep 2015 13:25:56 +0000</pubDate>
      <guid>https://www.scrivano.org/2015/09/30/ostree-docker-builder/</guid>
      <description>&lt;p&gt;rpm-ostree, used together with OStree, is a powerful tool to generate immutable images for .rpm based systems, so why not use it for generating Docker images as well? rpm-ostree already has support for composing a container tree, but the steps to go from an OStree commit to a ready-to-run Docker image involve several manual operations. ostree-docker-builder is a small tool that automates this workflow, taking a JSON package description and producing a tagged Docker image with a minimal Dockerfile.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Create a QCOW2 image for Fedora 22 Atomic</title>
      <link>https://www.scrivano.org/posts/2015-04-20-create-a-qcow2-image-for-fedora-22-atomic/</link>
      <pubDate>Mon, 20 Apr 2015 15:50:30 +0000</pubDate>
      <guid>https://www.scrivano.org/posts/2015-04-20-create-a-qcow2-image-for-fedora-22-atomic/</guid>
      <description>&lt;p&gt;This tutorial shows how to create a QCOW2 image that can be directly imported via virt-install to test out Fedora 22 Atomic starting from a custom OStree repo. The process involves composing an OStree repository from a Fedora Atomic tree definition, serving it over HTTP so the installer can reach it, then driving an unattended installation through a kickstart file. This gives you full control over the package set and tree composition rather than relying on a pre-built official image.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
