Merge pull request #684 from buildpacks/fix/custom-env

Fix summaries for "custom env" page and add link to podman from main …

docs/app-journey/index.html

@@ -874,9 +874,10 @@ <h1 class="title">An App&rsquo;s Brief Journey from Source to Image</h1>
 
         <h2 id="pack-for-the-journey">Pack for the journey</h2>
 <p>In this tutorial, we&rsquo;ll explain how to use <code>pack</code> and <strong>buildpacks</strong> to create a runnable app image from source code.</p>
-<p>In order to run the build process in an isolated fashion, <code>pack</code> uses <strong>Docker</strong>. That means you&rsquo;ll need to make sure you have both <code>docker</code> and <code>pack</code> installed:</p>
-<a href='https://store.docker.com/search?type=edition&amp;offering=community' class='download-button button icon-button bg-blue'> Install Docker </a><br />
+<p>In order to run the build process in an isolated fashion, <code>pack</code> uses <strong>Docker</strong> or a Docker-compatible daemon to create the containers where buildpacks execute.
+That means you&rsquo;ll need to make sure you have both <code>pack</code> and a daemon installed:</p>
 <a href='/docs/install-pack' class='download-button button icon-button bg-pink'> Install pack </a><br />
+<p><a href='https://store.docker.com/search?type=edition&amp;offering=community' class='download-button button icon-button bg-blue'> Install Docker </a><br /> or alternatively, see <a href="/docs/for-app-developers/how-to/special-cases/build-on-podman">this page</a> about working with <code>podman</code>.</p>
 <blockquote>
 <p><strong>NOTE:</strong> <code>pack</code> is only one implementation of the <a href="https://github.com/buildpacks/spec/blob/main/platform.md">Cloud Native Buildpacks Platform Specification</a>. Additionally, not all Cloud Native Buildpacks Platforms require Docker.</p>
 </blockquote>

docs/for-app-developers/how-to/special-cases/build-for-windows/index.html

@@ -8,9 +8,8 @@
 <meta charset="utf-8">
 <meta http-equiv="x-ua-compatible" content="ie=edge">
 <meta name="viewport" content="width=device-width, initial-scale=1, shrink-to-fit=no">
-<meta name="description" content="EXPERIMENTAL Windows support is experimental!
-Enable experimental mode by running: pack config experimental true
-Before You Start Recommended reading Before trying out builds for Windows images, we…"/>
+<meta name="description" content="You can use buildpacks to build container images that run Windows containers on Windows (WCOW).
+This page is not relevant if your host machine is Windows but you are running Linux containers on…"/>
 <link rel="canonical" content="https://buildpacks.io/docs/for-app-developers/how-to/special-cases/build-for-windows/">
 <link rel="icon" type="image/png" href="/images/favicon.png">
 
@@ -24,9 +23,8 @@
 <meta property="og:url" content="https://buildpacks.io/docs/for-app-developers/how-to/special-cases/build-for-windows/">
 <meta property="og:locale" content="en_US">
 <meta property="og:site_name" content="Cloud Native Buildpacks">
-<meta property="og:description" content="EXPERIMENTAL Windows support is experimental!
-Enable experimental mode by running: pack config experimental true
-Before You Start Recommended reading Before trying out builds for Windows images, we…">
+<meta property="og:description" content="You can use buildpacks to build container images that run Windows containers on Windows (WCOW).
+This page is not relevant if your host machine is Windows but you are running Linux containers on…">
 <meta property="og:type" content="article">
 <meta property="og:image" content="https://buildpacks.io/images/buildpacks-social-card.jpg">
 <meta property="og:image:alt" content="Buildpacks project logo">
@@ -874,7 +872,10 @@
           <h1 class="title">Build for Windows containers</h1>
         </div>
 
-        <blockquote>
+        <p>You can use buildpacks to build container images that run Windows containers on Windows (WCOW).</p>
+<p>This page is not relevant if your host machine is Windows but you are running Linux containers on Windows (LCOW);
+in this case, no special configuration is required.</p>
+<blockquote>
 <p><strong>EXPERIMENTAL</strong> Windows support is experimental!</p>
 <p>Enable experimental mode by running: <code>pack config experimental true</code></p>
 </blockquote>

docs/for-app-developers/how-to/special-cases/export-to-oci-layout/index.html

@@ -8,7 +8,7 @@
 <meta charset="utf-8">
 <meta http-equiv="x-ua-compatible" content="ie=edge">
 <meta name="viewport" content="width=device-width, initial-scale=1, shrink-to-fit=no">
-<meta name="description" content="The OCI Image Layout is the directory structure for OCI content-addressable blobs and location-addressable references. See the specification. Exporting to OCI layout format is an experimental feature…"/>
+<meta name="description" content="The OCI Image Layout is the directory structure for OCI content-addressable blobs and location-addressable references."/>
 <link rel="canonical" content="https://buildpacks.io/docs/for-app-developers/how-to/special-cases/export-to-oci-layout/">
 <link rel="icon" type="image/png" href="/images/favicon.png">
 
@@ -22,7 +22,7 @@
 <meta property="og:url" content="https://buildpacks.io/docs/for-app-developers/how-to/special-cases/export-to-oci-layout/">
 <meta property="og:locale" content="en_US">
 <meta property="og:site_name" content="Cloud Native Buildpacks">
-<meta property="og:description" content="The OCI Image Layout is the directory structure for OCI content-addressable blobs and location-addressable references. See the specification. Exporting to OCI layout format is an experimental feature…">
+<meta property="og:description" content="The OCI Image Layout is the directory structure for OCI content-addressable blobs and location-addressable references.">
 <meta property="og:type" content="article">
 <meta property="og:image" content="https://buildpacks.io/images/buildpacks-social-card.jpg">
 <meta property="og:image:alt" content="Buildpacks project logo">

docs/for-app-developers/how-to/special-cases/index.html

@@ -889,24 +889,17 @@ <h2><a href="https://buildpacks.io/docs/for-app-developers/how-to/special-cases/
             </div>
 
           <h2><a href="https://buildpacks.io/docs/for-app-developers/how-to/special-cases/build-for-windows/" class="">Build for Windows containers</a></h2>
-          <p class="m-1">EXPERIMENTAL Windows support is experimental!
-Enable experimental mode by running: pack config experimental true
-Before You Start Recommended reading Before trying out builds for Windows images, we recommend following the Linux image tutorial under Getting Started. Don’t worry, you can still run it on a Windows OS if you need to – just make sure to enable Linux containers for Docker first.
-When you’re done, head back here.
-Enable Windows container mode In order to produce Windows container images, ensure Windows container mode is enabled in your Docker settings (available only in Docker for Windows).</p>
+          <p class="m-1"><p>You can use buildpacks to build container images that run Windows containers on Windows (WCOW).</p>
+<p>This page is not relevant if your host machine is Windows but you are running Linux containers on Windows (LCOW);
+in this case, no special configuration is required.</p></p>
 
 
             <div class="text-md-right">
               <a class="small text-pink mr-md-3 text-decoration-none" href="https://buildpacks.io/docs/for-app-developers/how-to/special-cases/build-for-windows/">Learn more →</a>
             </div>
 
           <h2><a href="https://buildpacks.io/docs/for-app-developers/how-to/special-cases/export-to-oci-layout/" class="">Export to OCI layout format on disk</a></h2>
-          <p class="m-1"><p>The OCI Image Layout is the directory structure for OCI content-addressable blobs and location-addressable references. See the specification. Exporting to OCI layout format is an experimental feature available on pack since version 0.30.0</p>
-<ol>
-<li>Enable experimental feature Verify your pack version is equal or greater than 0.30.0
-pack version Enable the experimental features on pack
-pack config experimental true You can confirm everything is fine, checking the config.toml file in your PACK_HOME installation folder.</li>
-</ol></p>
+          <p class="m-1">The OCI Image Layout is the directory structure for OCI content-addressable blobs and location-addressable references.</p>
 
 
             <div class="text-md-right">

docs/for-app-developers/how-to/special-cases/index.xml

@@ -19,14 +19,14 @@
       <link>https://buildpacks.io/docs/for-app-developers/how-to/special-cases/build-for-windows/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       <guid>https://buildpacks.io/docs/for-app-developers/how-to/special-cases/build-for-windows/</guid>
-      <description>EXPERIMENTAL Windows support is experimental!&#xA;Enable experimental mode by running: pack config experimental true&#xA;Before You Start Recommended reading Before trying out builds for Windows images, we recommend following the Linux image tutorial under Getting Started. Don&amp;rsquo;t worry, you can still run it on a Windows OS if you need to &amp;ndash; just make sure to enable Linux containers for Docker first.&#xA;When you&amp;rsquo;re done, head back here.&#xA;Enable Windows container mode In order to produce Windows container images, ensure Windows container mode is enabled in your Docker settings (available only in Docker for Windows).</description>
+      <description>&lt;p&gt;You can use buildpacks to build container images that run Windows containers on Windows (WCOW).&lt;/p&gt;&#xA;&lt;p&gt;This page is not relevant if your host machine is Windows but you are running Linux containers on Windows (LCOW);&#xA;in this case, no special configuration is required.&lt;/p&gt;</description>
     </item>
     <item>
       <title>Export to OCI layout format on disk</title>
       <link>https://buildpacks.io/docs/for-app-developers/how-to/special-cases/export-to-oci-layout/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       <guid>https://buildpacks.io/docs/for-app-developers/how-to/special-cases/export-to-oci-layout/</guid>
-      <description>The OCI Image Layout is the directory structure for OCI content-addressable blobs and location-addressable references. See the specification. Exporting to OCI layout format is an experimental feature available on pack since version 0.30.0&#xA;1. Enable experimental feature Verify your pack version is equal or greater than 0.30.0&#xA;pack version Enable the experimental features on pack&#xA;pack config experimental true You can confirm everything is fine, checking the config.toml file in your PACK_HOME installation folder.</description>
+      <description>The OCI Image Layout is the directory structure for OCI content-addressable blobs and location-addressable references.</description>
     </item>
     <item>
       <title>Use an HTTP proxy</title>

docs/index.xml

@@ -12,7 +12,7 @@
       <link>https://buildpacks.io/docs/app-journey/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       <guid>https://buildpacks.io/docs/app-journey/</guid>
-      <description>Pack for the journey In this tutorial, we&amp;rsquo;ll explain how to use pack and buildpacks to create a runnable app image from source code.&#xA;In order to run the build process in an isolated fashion, pack uses Docker. That means you&amp;rsquo;ll need to make sure you have both docker and pack installed:&#xA;Install Docker Install pack NOTE: pack is only one implementation of the Cloud Native Buildpacks Platform Specification. Additionally, not all Cloud Native Buildpacks Platforms require Docker.</description>
+      <description>Pack for the journey In this tutorial, we&amp;rsquo;ll explain how to use pack and buildpacks to create a runnable app image from source code.&#xA;In order to run the build process in an isolated fashion, pack uses Docker or a Docker-compatible daemon to create the containers where buildpacks execute. That means you&amp;rsquo;ll need to make sure you have both pack and a daemon installed:&#xA;Install pack Install Docker or alternatively, see this page about working with podman.</description>
     </item>
   </channel>
 </rss>

index.xml

@@ -145,14 +145,14 @@
       <link>https://buildpacks.io/docs/app-journey/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       <guid>https://buildpacks.io/docs/app-journey/</guid>
-      <description>Pack for the journey In this tutorial, we&amp;rsquo;ll explain how to use pack and buildpacks to create a runnable app image from source code.&#xA;In order to run the build process in an isolated fashion, pack uses Docker. That means you&amp;rsquo;ll need to make sure you have both docker and pack installed:&#xA;Install Docker Install pack NOTE: pack is only one implementation of the Cloud Native Buildpacks Platform Specification. Additionally, not all Cloud Native Buildpacks Platforms require Docker.</description>
+      <description>Pack for the journey In this tutorial, we&amp;rsquo;ll explain how to use pack and buildpacks to create a runnable app image from source code.&#xA;In order to run the build process in an isolated fashion, pack uses Docker or a Docker-compatible daemon to create the containers where buildpacks execute. That means you&amp;rsquo;ll need to make sure you have both pack and a daemon installed:&#xA;Install pack Install Docker or alternatively, see this page about working with podman.</description>
     </item>
     <item>
       <title>Build for Windows containers</title>
       <link>https://buildpacks.io/docs/for-app-developers/how-to/special-cases/build-for-windows/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       <guid>https://buildpacks.io/docs/for-app-developers/how-to/special-cases/build-for-windows/</guid>
-      <description>EXPERIMENTAL Windows support is experimental!&#xA;Enable experimental mode by running: pack config experimental true&#xA;Before You Start Recommended reading Before trying out builds for Windows images, we recommend following the Linux image tutorial under Getting Started. Don&amp;rsquo;t worry, you can still run it on a Windows OS if you need to &amp;ndash; just make sure to enable Linux containers for Docker first.&#xA;When you&amp;rsquo;re done, head back here.&#xA;Enable Windows container mode In order to produce Windows container images, ensure Windows container mode is enabled in your Docker settings (available only in Docker for Windows).</description>
+      <description>&lt;p&gt;You can use buildpacks to build container images that run Windows containers on Windows (WCOW).&lt;/p&gt;&#xA;&lt;p&gt;This page is not relevant if your host machine is Windows but you are running Linux containers on Windows (LCOW);&#xA;in this case, no special configuration is required.&lt;/p&gt;</description>
     </item>
     <item>
       <title>builder.toml</title>
@@ -327,7 +327,7 @@
       <link>https://buildpacks.io/docs/for-app-developers/how-to/special-cases/export-to-oci-layout/</link>
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       <guid>https://buildpacks.io/docs/for-app-developers/how-to/special-cases/export-to-oci-layout/</guid>
-      <description>The OCI Image Layout is the directory structure for OCI content-addressable blobs and location-addressable references. See the specification. Exporting to OCI layout format is an experimental feature available on pack since version 0.30.0&#xA;1. Enable experimental feature Verify your pack version is equal or greater than 0.30.0&#xA;pack version Enable the experimental features on pack&#xA;pack config experimental true You can confirm everything is fine, checking the config.toml file in your PACK_HOME installation folder.</description>
+      <description>The OCI Image Layout is the directory structure for OCI content-addressable blobs and location-addressable references.</description>
     </item>
     <item>
       <title>Mount volumes at build-time</title>