<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Containerization on Rachid Youven Zeghlache</title><link>https://youvenz.github.io/tags/containerization/</link><description>Recent content in Containerization on Rachid Youven Zeghlache</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 05 Mar 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://youvenz.github.io/tags/containerization/index.xml" rel="self" type="application/rss+xml"/><item><title>Anaconda to Apptainer: Reproducible Python Environments</title><link>https://youvenz.github.io/blog/2026-03-05-anaconda-to-apptainer-reproducible-python-environments/</link><pubDate>Thu, 05 Mar 2026 00:00:00 +0000</pubDate><guid>https://youvenz.github.io/blog/2026-03-05-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;
&lt;p&gt;Missing libraries. Version conflicts. Runtime errors at 3 AM when your job finally reaches the queue. The problem: &lt;strong&gt;your local Conda environment doesn&amp;rsquo;t travel.&lt;/strong&gt; It&amp;rsquo;s fragile, system-dependent, and impossible to reproduce across different machines.&lt;/p&gt;</description></item><item><title>Apptainer &amp; Conda: Reproducible HPC Python Environments</title><link>https://youvenz.github.io/blog/2026-03-05-apptainer-conda-reproducible-hpc-python-environments/</link><pubDate>Thu, 05 Mar 2026 00:00:00 +0000</pubDate><guid>https://youvenz.github.io/blog/2026-03-05-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;
&lt;p&gt;This is the researcher&amp;rsquo;s tax: &lt;strong&gt;environment reproduction across machines is broken by default.&lt;/strong&gt;&lt;/p&gt;
&lt;h2 id="what-this-solves"&gt;What This Solves&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;Apptainer&lt;/strong&gt; (formerly Singularity) is a containerization tool built for HPC clusters. Unlike Docker, it doesn&amp;rsquo;t require root privileges and integrates seamlessly with cluster job schedulers like SLURM and PBS. Combined with &lt;strong&gt;Conda&lt;/strong&gt;, it lets you package a complete, reproducible Python environment—dependencies, versions, and all—into a single &lt;code&gt;.sif&lt;/code&gt; file that runs identically on your laptop, your colleague&amp;rsquo;s machine, and any HPC node.&lt;/p&gt;</description></item><item><title>Master Apptainer in 25 Minutes: Build Reproducible Python Environments</title><link>https://youvenz.github.io/blog/2026-03-05-master-apptainer-in-25-minutes-build-reproducible-python-env/</link><pubDate>Thu, 05 Mar 2026 00:00:00 +0000</pubDate><guid>https://youvenz.github.io/blog/2026-03-05-master-apptainer-in-25-minutes-build-reproducible-python-env/</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;
&lt;p&gt;This is &lt;strong&gt;dependency hell&lt;/strong&gt;, and it&amp;rsquo;s the silent killer of reproducible science.&lt;/p&gt;</description></item><item><title>SSH &amp; SLURM: Transfer Code to HPC Clusters</title><link>https://youvenz.github.io/blog/2026-03-05-ssh-slurm-transfer-code-to-hpc-clusters/</link><pubDate>Thu, 05 Mar 2026 00:00:00 +0000</pubDate><guid>https://youvenz.github.io/blog/2026-03-05-ssh-slurm-transfer-code-to-hpc-clusters/</guid><description>&lt;h2 id="transfer-code-to-hpc-clusters-using-ssh-singularityapptainer--slurm"&gt;Transfer Code to HPC Clusters Using SSH, Singularity/Apptainer &amp;amp; SLURM&lt;/h2&gt;
&lt;p&gt;You&amp;rsquo;ve written working code on your laptop. Now you need to run it on your institution&amp;rsquo;s HPC cluster with 100+ GPUs—but you&amp;rsquo;re staring at a terminal with no idea how to get your files there, containerize your environment, or submit a job without breaking it.&lt;/p&gt;
&lt;p&gt;This is the moment most researchers feel lost.&lt;/p&gt;
&lt;h2 id="the-hpc-stack-in-90-seconds"&gt;The HPC Stack in 90 Seconds&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;High-performance computing (HPC) clusters&lt;/strong&gt; are shared servers with massive CPU and GPU resources. To use them safely and reproducibly, you need three tools working together:&lt;/p&gt;</description></item></channel></rss>