<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Apptainer on The Augmented Scholar</title><link>https://augmentedscholars.com/tags/apptainer/</link><description>Recent content in Apptainer on The Augmented Scholar</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 17 Jul 2026 17:59:48 +0400</lastBuildDate><atom:link href="https://augmentedscholars.com/tags/apptainer/index.xml" rel="self" type="application/rss+xml"/><item><title>Anaconda to Apptainer: Reproducible Python Environments</title><link>https://augmentedscholars.com/posts/code-automation/anaconda-to-apptainer-reproducible-python-environments/</link><pubDate>Thu, 05 Mar 2026 00:00:00 +0000</pubDate><guid>https://augmentedscholars.com/posts/code-automation/anaconda-to-apptainer-reproducible-python-environments/</guid><description>&lt;h1 id="build-reproducible-python-environments-with-anaconda-to-apptainer--without-broken-hpc-deployments"&gt;Build Reproducible Python Environments with Anaconda to Apptainer — Without Broken HPC Deployments&lt;/h1&gt;
&lt;p&gt;You&amp;rsquo;ve spent weeks perfecting a Python environment locally. Dependencies are locked in. Your code runs flawlessly on your laptop. Then you push it to the HPC cluster, and everything breaks.&lt;/p&gt;</description></item><item><title>Apptainer &amp; Conda: Reproducible HPC Python Environments</title><link>https://augmentedscholars.com/posts/code-automation/apptainer-conda-reproducible-hpc-python-environments/</link><pubDate>Thu, 05 Mar 2026 00:00:00 +0000</pubDate><guid>https://augmentedscholars.com/posts/code-automation/apptainer-conda-reproducible-hpc-python-environments/</guid><description>&lt;h1 id="build-reproducible-python-environments-with-apptainer--conda--for-hpc-researchers"&gt;Build Reproducible Python Environments with Apptainer &amp;amp; Conda — For HPC Researchers&lt;/h1&gt;
&lt;p&gt;Your Python script runs perfectly on your laptop. You transfer it to the cluster. Runtime fails. Missing dependencies. Version conflicts. Different Python builds. You spend hours debugging environment mismatches instead of running science.&lt;/p&gt;</description></item><item><title>Apptainer Fundamentals: Building Your First Container</title><link>https://augmentedscholars.com/posts/code-automation/apptainer-fundamentals-building-your-first-container/</link><pubDate>Thu, 05 Mar 2026 00:00:00 +0000</pubDate><guid>https://augmentedscholars.com/posts/code-automation/apptainer-fundamentals-building-your-first-container/</guid><description>&lt;h1 id="build-your-first-apptainer-container-without-docker--a-practical-guide-for-hpc-researchers"&gt;Build Your First Apptainer Container Without Docker — A Practical Guide for HPC Researchers&lt;/h1&gt;
&lt;p&gt;You&amp;rsquo;ve got HPC cluster access, but containerizing your workflow feels like a black box. &lt;strong&gt;Singularity (now Apptainer) promises reproducibility and portability&lt;/strong&gt;, but the documentation jumps between concepts, and you&amp;rsquo;re not sure where to start. You don&amp;rsquo;t want to learn Docker first—you just want a working container on your cluster &lt;em&gt;today&lt;/em&gt;.&lt;/p&gt;</description></item><item><title>Master Apptainer in 25 Minutes: Build Reproducible Python Environments</title><link>https://augmentedscholars.com/posts/code-automation/master-apptainer-in-25-minutes-build-reproducible-python-environments/</link><pubDate>Thu, 05 Mar 2026 00:00:00 +0000</pubDate><guid>https://augmentedscholars.com/posts/code-automation/master-apptainer-in-25-minutes-build-reproducible-python-environments/</guid><description>&lt;h1 id="build-reproducible-python-environments-with-apptainer-singularity--for-researchers-tired-of-it-works-on-my-machine"&gt;Build Reproducible Python Environments with Apptainer (Singularity) — For Researchers Tired of &amp;ldquo;It Works on My Machine&amp;rdquo;&lt;/h1&gt;
&lt;p&gt;Your Python script runs flawlessly on your laptop. Your colleague runs it on theirs and gets import errors. You submit it to the HPC cluster and it crashes with missing CUDA libraries. You spend three hours debugging version conflicts instead of doing research.&lt;/p&gt;</description></item><item><title>Singularity/Apptainer: Local to Cluster Workflow</title><link>https://augmentedscholars.com/posts/code-automation/singularityapptainer-local-to-cluster-workflow/</link><pubDate>Thu, 05 Mar 2026 00:00:00 +0000</pubDate><guid>https://augmentedscholars.com/posts/code-automation/singularityapptainer-local-to-cluster-workflow/</guid><description>&lt;h1 id="pull-build-and-deploy-singularity-containers-from-local-machine-to-hpc-clusters"&gt;Pull, Build, and Deploy Singularity Containers from Local Machine to HPC Clusters&lt;/h1&gt;
&lt;p&gt;You&amp;rsquo;ve got terabytes of data on your HPC cluster and a Python script that works on your laptop. But moving it to the cluster means wrestling with dependency conflicts, mysterious &lt;code&gt;ModuleNotFoundError&lt;/code&gt; messages, and copying massive datasets you don&amp;rsquo;t want to duplicate. You need a way to package your entire development environment—dependencies, libraries, Python versions—and run it anywhere without breaking it. That&amp;rsquo;s where &lt;strong&gt;Singularity/Apptainer&lt;/strong&gt; comes in.&lt;/p&gt;</description></item></channel></rss>