<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Dockerlinux</title>
    <description>The latest articles on DEV Community by Dockerlinux (@dockerlinux).</description>
    <link>https://dev.to/dockerlinux</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4141846%2Fc9a4b610-06ba-4cac-88b5-4ca046cc9f6d.png</url>
      <title>DEV Community: Dockerlinux</title>
      <link>https://dev.to/dockerlinux</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/dockerlinux"/>
    <language>en</language>
    <item>
      <title>What's new on DockerLinux 🐧</title>
      <dc:creator>Dockerlinux</dc:creator>
      <pubDate>Wed, 14 Oct 2026 15:38:15 +0000</pubDate>
      <link>https://dev.to/dockerlinux/whats-new-on-dockerlinux-195f</link>
      <guid>https://dev.to/dockerlinux/whats-new-on-dockerlinux-195f</guid>
      <description>&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fnpb3xgsvbco6ohzfdcki.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fnpb3xgsvbco6ohzfdcki.png" alt="New Update" width="800" height="1000"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Three updates to DockerLinux this week, the first one straight from a player's feedback:&lt;/p&gt;

&lt;p&gt;→ Replay a level for the star you missed. Before, the only way to improve a level's stars was "Reset progress" and losing everything. Now finished levels have a Replay button: a fresh machine, the same missions, and your XP and other levels stay exactly as they were. Stars can only go up. New badge: Perfectionist.&lt;br&gt;
→ Terminal colour themes for players with a free account, saved with the account so they follow you to every computer. Errors stay red in every theme.&lt;br&gt;
→ 16 free command guides at dockerlinux.com/commands, now including cat, cp, mv, rm, docker build and docker compose, each with a live terminal on the page.&lt;/p&gt;

&lt;p&gt;Feedback from players shapes what gets built next. What should come next?&lt;/p&gt;

&lt;h1&gt;
  
  
  BuildInPublic #Linux #Docker #DevOps
&lt;/h1&gt;

</description>
      <category>linux</category>
      <category>docker</category>
      <category>dockerlinux</category>
      <category>coding</category>
    </item>
    <item>
      <title>DockerLinux update: a broken server every day, and free command guides with a live terminal</title>
      <dc:creator>Dockerlinux</dc:creator>
      <pubDate>Mon, 12 Oct 2026 17:00:00 +0000</pubDate>
      <link>https://dev.to/dockerlinux/dockerlinux-update-a-broken-server-every-day-and-free-command-guides-with-a-live-terminal-4mh6</link>
      <guid>https://dev.to/dockerlinux/dockerlinux-update-a-broken-server-every-day-and-free-command-guides-with-a-live-terminal-4mh6</guid>
      <description>&lt;p&gt;&lt;a href="https://dockerlinux.com/?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=update-oct12" rel="noopener noreferrer"&gt;DockerLinux&lt;/a&gt; is my free browser game for learning Linux and Docker: you type real commands into a simulated machine and finish missions. A batch of updates just went live. Here's what changed and why.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. Daily Incident: one broken server a day, the same for everyone
&lt;/h2&gt;

&lt;p&gt;The on-call incidents put you on a pretend production server that's down, and you fix it against the clock. Now there's a new one every day:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="nv"&gt;$ &lt;/span&gt;oncall daily
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Same server for every player&lt;/strong&gt;, so you can compare notes (without spoilers).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Mondays are easy, Saturdays are hard.&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Free, no account needed.&lt;/strong&gt; It opens after Level 7.&lt;/li&gt;
&lt;li&gt;Fix it and you get stars, XP and a &lt;strong&gt;spoiler-free result&lt;/strong&gt; to copy or share: squares, your time, hints used and your streak.&lt;/li&gt;
&lt;li&gt;The card shows how many players fixed today's server, and whether you were faster than most.&lt;/li&gt;
&lt;li&gt;Three new badges: Morning Pager, Seven Pages and Pager Perfect.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  2. Free command guides, each with a live terminal
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://dockerlinux.com/commands/?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=update-oct12" rel="noopener noreferrer"&gt;dockerlinux.com/commands&lt;/a&gt; explains &lt;code&gt;ls&lt;/code&gt;, &lt;code&gt;cd&lt;/code&gt;, &lt;code&gt;grep&lt;/code&gt;, &lt;code&gt;find&lt;/code&gt;, &lt;code&gt;chmod&lt;/code&gt;, &lt;code&gt;tar&lt;/code&gt;, &lt;code&gt;kill&lt;/code&gt;, &lt;code&gt;docker run&lt;/code&gt;, &lt;code&gt;docker ps&lt;/code&gt; and &lt;code&gt;docker logs&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;Every page has:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;a &lt;strong&gt;live terminal on the page&lt;/strong&gt;, so you try the command right where you read about it&lt;/li&gt;
&lt;li&gt;examples with a &lt;strong&gt;▶ Run&lt;/strong&gt; button&lt;/li&gt;
&lt;li&gt;the options you'll actually use, plus tips&lt;/li&gt;
&lt;li&gt;a link to the level that teaches it&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The &lt;code&gt;chmod&lt;/code&gt; page has a permission calculator: tick the boxes, get &lt;code&gt;755&lt;/code&gt;. In the game, &lt;code&gt;man chmod&lt;/code&gt; and &lt;code&gt;chmod --help&lt;/code&gt; end with the guide's address, and a 📖 link takes you from a lesson to its guide. On the World map, each island now has a Command Library with that island's guides.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. "Your commands": a cheat sheet that fills in as you play
&lt;/h2&gt;

&lt;p&gt;Under the missions, each command of the level starts as &lt;code&gt;???&lt;/code&gt; and unlocks (&lt;code&gt;pwd&lt;/code&gt; + what it did) as you finish its task. By the end of a level you've built its cheat sheet yourself. "What you just learned" keeps the newest lesson in view, so it doesn't scroll away or vanish with &lt;code&gt;clear&lt;/code&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  4. Engine State, always in sight
&lt;/h2&gt;

&lt;p&gt;The live Docker panel used to sit at the bottom of the sidebar, where you had to scroll to find it. Now a thin rail beside the terminal always shows how many containers are running and how many images, networks and volumes you have. A number flashes when your command changes it. Click it and the full details slide in, and they stay open while you type, so you can watch &lt;code&gt;docker run&lt;/code&gt; and &lt;code&gt;docker rm&lt;/code&gt; change them.&lt;/p&gt;

&lt;h2&gt;
  
  
  Also
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Prof. Kernel-Panic now introduces each level in the terminal, and the new &lt;strong&gt;Terminal Guru&lt;/strong&gt; easter egg (&lt;code&gt;guru&lt;/code&gt;) gives his advice on the level you're in.&lt;/li&gt;
&lt;li&gt;Everything is in English and Brazilian Portuguese. Commands stay in English, like on a real server.&lt;/li&gt;
&lt;/ul&gt;




&lt;p&gt;Try today's Daily Incident: &lt;a href="https://dockerlinux.com/?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=update-oct12" rel="noopener noreferrer"&gt;dockerlinux.com&lt;/a&gt;. It's free, and there's nothing to install.&lt;/p&gt;

&lt;p&gt;Which command should get a guide next? 👇&lt;/p&gt;

</description>
      <category>docker</category>
      <category>linux</category>
      <category>devops</category>
      <category>game</category>
    </item>
    <item>
      <title>Your Docker container didn't vanish. Here's how to find out why it stopped</title>
      <dc:creator>Dockerlinux</dc:creator>
      <pubDate>Sun, 11 Oct 2026 13:00:00 +0000</pubDate>
      <link>https://dev.to/dockerlinux/your-docker-container-didnt-vanish-heres-how-to-find-out-why-it-stopped-5a9e</link>
      <guid>https://dev.to/dockerlinux/your-docker-container-didnt-vanish-heres-how-to-find-out-why-it-stopped-5a9e</guid>
      <description>&lt;p&gt;"My container disappeared" is one of the most common things people say when they start with Docker. It almost never disappeared. It stopped. Here's the five-step routine to find out why.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. List all containers, not just the running ones
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="nv"&gt;$ &lt;/span&gt;docker ps
CONTAINER ID   IMAGE   COMMAND   CREATED   STATUS   PORTS   NAMES

&lt;span class="nv"&gt;$ &lt;/span&gt;docker ps &lt;span class="nt"&gt;-a&lt;/span&gt;
CONTAINER ID   IMAGE        COMMAND                  CREATED          STATUS                     PORTS   NAMES
3f2a9c1e8b7d   nginx:1.27   &lt;span class="s2"&gt;"/docker-entrypoint.…"&lt;/span&gt;   10 minutes ago   Exited &lt;span class="o"&gt;(&lt;/span&gt;1&lt;span class="o"&gt;)&lt;/span&gt; 2 minutes ago           web
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;code&gt;docker ps&lt;/code&gt; only shows running containers. &lt;code&gt;-a&lt;/code&gt; shows all of them.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. Read the exit code
&lt;/h2&gt;

&lt;p&gt;The number in &lt;code&gt;Exited (…)&lt;/code&gt; is the exit code of the container's main process. You can also ask for it directly:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;docker inspect &lt;span class="nt"&gt;--format&lt;/span&gt; &lt;span class="s1"&gt;'{{.State.ExitCode}}'&lt;/span&gt; web
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;A few you'll see often:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Exit code&lt;/th&gt;
&lt;th&gt;Usually means&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;0&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;The main process finished normally (a one-off job, or a command with nothing to keep it running)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;1&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;The app crashed or failed to start&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;137&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;Killed with SIGKILL (128 + 9), often because it ran out of memory&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;143&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;Stopped with SIGTERM (128 + 15), for example by &lt;code&gt;docker stop&lt;/code&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;For a 137, check whether the kernel's out-of-memory killer did it:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;docker inspect &lt;span class="nt"&gt;--format&lt;/span&gt; &lt;span class="s1"&gt;'{{.State.OOMKilled}}'&lt;/span&gt; web
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  3. Read the logs before restarting
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;docker logs &lt;span class="nt"&gt;--tail&lt;/span&gt; 50 web
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The last lines usually name the problem: a missing environment variable, a port already in use, a config file that isn't there. Restarting first just hides the error until it happens again.&lt;/p&gt;

&lt;h2&gt;
  
  
  4. Remember: a container lives as long as its main process
&lt;/h2&gt;

&lt;p&gt;If the main process ends, the container ends, even if nothing went wrong. That's why &lt;code&gt;docker run ubuntu&lt;/code&gt; exits straight away: it starts a shell, the shell has no input, and it finishes. Long-running services (a web server, a database) keep their main process in the foreground on purpose.&lt;/p&gt;

&lt;h2&gt;
  
  
  5. Bring it back, and make it come back by itself
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;docker start web
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;If it stopped because the machine rebooted, give it a restart policy so it comes back on its own next time:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;docker update &lt;span class="nt"&gt;--restart&lt;/span&gt; unless-stopped web
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;code&gt;unless-stopped&lt;/code&gt; restarts the container after a reboot or a crash, unless you stopped it yourself.&lt;/p&gt;

&lt;h2&gt;
  
  
  The short version
&lt;/h2&gt;

&lt;p&gt;&lt;code&gt;docker ps -a&lt;/code&gt; → exit code → &lt;code&gt;docker logs&lt;/code&gt; → fix → &lt;code&gt;docker start&lt;/code&gt;, and set a restart policy for anything that must survive a reboot.&lt;/p&gt;




&lt;p&gt;If you'd like to practise this on a pretend production server, &lt;a href="https://dockerlinux.com/?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=daily-w1" rel="noopener noreferrer"&gt;DockerLinux&lt;/a&gt; (my free browser game for learning Linux and Docker) has an on-call incident built around exactly this situation: the server rebooted and the shop is down.&lt;/p&gt;

&lt;p&gt;What's the strangest reason you've found for a container that "disappeared"? 👇&lt;/p&gt;

</description>
      <category>docker</category>
      <category>linux</category>
      <category>containers</category>
      <category>devops</category>
    </item>
    <item>
      <title>I turned my terminal game into an isometric world (plain SVG + Vue, no game engine)</title>
      <dc:creator>Dockerlinux</dc:creator>
      <pubDate>Tue, 06 Oct 2026 19:25:30 +0000</pubDate>
      <link>https://dev.to/dockerlinux/i-turned-my-terminal-game-into-an-isometric-world-plain-svg-vue-no-game-engine-2pla</link>
      <guid>https://dev.to/dockerlinux/i-turned-my-terminal-game-into-an-isometric-world-plain-svg-vue-no-game-engine-2pla</guid>
      <description>&lt;p&gt;&lt;a href="https://dockerlinux.com/?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=world" rel="noopener noreferrer"&gt;DockerLinux&lt;/a&gt; is my free browser game for learning Linux and Docker in a simulated terminal. Until this week it was one terminal and a list of levels. Now every level is a building on a map of islands: finish one in the terminal, and the path to the next lights up while Byte, our pixel penguin, walks there.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fxzlhf9ih55vfpcj230f0.gif" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fxzlhf9ih55vfpcj230f0.gif" alt="Finishing a level: the path lights up and Byte walks across the bridge to Docker Harbour" width="800" height="450"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;No canvas, no game engine. It's SVG drawn by Vue, and a small pure-JavaScript module that decides what goes where. Here's how it works.&lt;/p&gt;

&lt;h2&gt;
  
  
  The map is data
&lt;/h2&gt;

&lt;p&gt;The whole world is built once, deterministically, from a few numbers per island:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight javascript"&gt;&lt;code&gt;&lt;span class="k"&gt;export&lt;/span&gt; &lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;ISLANDS&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;
  &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="na"&gt;id&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;linux&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;   &lt;span class="na"&gt;kind&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;linux&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;   &lt;span class="na"&gt;parts&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;[[&lt;/span&gt;&lt;span class="mi"&gt;9&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="mi"&gt;10&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="mf"&gt;5.6&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="mf"&gt;5.0&lt;/span&gt;&lt;span class="p"&gt;]],&lt;/span&gt;  &lt;span class="na"&gt;levels&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="mi"&gt;1&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="mi"&gt;2&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="mi"&gt;3&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="mi"&gt;4&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="mi"&gt;5&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt; &lt;span class="p"&gt;},&lt;/span&gt;
  &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="na"&gt;id&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;harbour&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="na"&gt;kind&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;harbour&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="na"&gt;parts&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;[[&lt;/span&gt;&lt;span class="mi"&gt;23&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="mi"&gt;8&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="mf"&gt;6.4&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="mf"&gt;5.6&lt;/span&gt;&lt;span class="p"&gt;]],&lt;/span&gt;  &lt;span class="na"&gt;levels&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="mi"&gt;6&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="mi"&gt;7&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="mi"&gt;8&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="mi"&gt;9&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="mi"&gt;10&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="mi"&gt;11&lt;/span&gt;&lt;span class="p"&gt;],&lt;/span&gt; &lt;span class="na"&gt;incidents&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="kc"&gt;true&lt;/span&gt; &lt;span class="p"&gt;},&lt;/span&gt;
  &lt;span class="c1"&gt;// … Sandbox Atoll, Linux Highlands, and two islands still in the fog&lt;/span&gt;
&lt;span class="p"&gt;]&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Each island is one or more ellipses on a shared tile grid (centre and radii, in tiles). A tiny hash wobbles the edge so coastlines don't look like perfect ovals, but it's a hash of the tile coordinates, not &lt;code&gt;Math.random()&lt;/code&gt;, so everyone gets exactly the same map and the tests can check it.&lt;/p&gt;

&lt;p&gt;Then:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Every level stands on a chosen tile&lt;/strong&gt; and gets a small building that matches its topic (a library for files, a crane for Compose, a vault for permissions…).&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Paths are routed between consecutive levels&lt;/strong&gt; with a little Dijkstra on the grid. Land is cheap, turns cost a bit extra (so roads look straight), and the sea is expensive but allowed, which is where the wooden bridges come from.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Free tiles get decoration&lt;/strong&gt;: trees on Linux Island, shipping containers in the harbour, mountains in the Highlands.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  The isometric part is two lines
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight javascript"&gt;&lt;code&gt;&lt;span class="c1"&gt;// grid → screen: the top-left of a 64 × 44 tile&lt;/span&gt;
&lt;span class="k"&gt;export&lt;/span&gt; &lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;iso&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;i&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nx"&gt;j&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;=&amp;gt;&lt;/span&gt; &lt;span class="p"&gt;({&lt;/span&gt; &lt;span class="na"&gt;x&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;i&lt;/span&gt; &lt;span class="o"&gt;-&lt;/span&gt; &lt;span class="nx"&gt;j&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;*&lt;/span&gt; &lt;span class="mi"&gt;32&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="na"&gt;y&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;i&lt;/span&gt; &lt;span class="o"&gt;+&lt;/span&gt; &lt;span class="nx"&gt;j&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;*&lt;/span&gt; &lt;span class="mi"&gt;16&lt;/span&gt; &lt;span class="p"&gt;})&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Draw in order of &lt;code&gt;i + j&lt;/code&gt; (back to front) and the overlap takes care of itself.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fq5sgt5i3jiytvk5l6vms.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fq5sgt5i3jiytvk5l6vms.png" alt="The World: Linux Island, Docker Harbour, Sandbox Atoll, Linux Highlands and two islands in the fog" width="800" height="450"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  The camera is just the viewBox
&lt;/h2&gt;

&lt;p&gt;Panning and zooming never move an element. They change the SVG's &lt;code&gt;viewBox&lt;/code&gt;: drag shifts it, the wheel or a pinch scales it around the pointer, and "fly to this island" animates it with &lt;code&gt;requestAnimationFrame&lt;/code&gt;. Everything is placed with SVG attributes, never inline styles, so the strict Content-Security-Policy stays happy. With &lt;code&gt;prefers-reduced-motion&lt;/code&gt;, the camera jumps instead of flying and Byte doesn't walk.&lt;/p&gt;

&lt;h2&gt;
  
  
  Missions as data (the new Linux Highlands)
&lt;/h2&gt;

&lt;p&gt;The five new advanced levels aren't in the public JavaScript bundle. The server sends them to logged-in players as JSON, which means their task checks can't be functions. They're data:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight javascript"&gt;&lt;code&gt;&lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="nl"&gt;id&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;hl_ps_kill&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nx"&gt;desc&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;Ask it to stop with kill and its PID&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="nx"&gt;check&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nl"&gt;any&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;
    &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="na"&gt;all&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;[{&lt;/span&gt; &lt;span class="na"&gt;ran&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;kill&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt; &lt;span class="p"&gt;},&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="na"&gt;args&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;(^|&lt;/span&gt;&lt;span class="se"&gt;\\&lt;/span&gt;&lt;span class="s1"&gt;s)4242(&lt;/span&gt;&lt;span class="se"&gt;\\&lt;/span&gt;&lt;span class="s1"&gt;s|$)&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt; &lt;span class="p"&gt;}]&lt;/span&gt; &lt;span class="p"&gt;},&lt;/span&gt;
    &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="na"&gt;all&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;[{&lt;/span&gt; &lt;span class="na"&gt;ran&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;pkill&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt; &lt;span class="p"&gt;},&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="na"&gt;args&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;miner&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt; &lt;span class="p"&gt;}]&lt;/span&gt; &lt;span class="p"&gt;},&lt;/span&gt;
  &lt;span class="p"&gt;]&lt;/span&gt; &lt;span class="p"&gt;},&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The browser compiles each spec into the same &lt;code&gt;(ctx) =&amp;gt; boolean&lt;/code&gt; the hand-written levels use. Anything unknown or malformed compiles to "never passes", so a bad item from the network can't crash the game. (And yes, that level has a crypto-miner at 97% CPU that politely ignores &lt;code&gt;kill&lt;/code&gt;. You need &lt;code&gt;kill -9&lt;/code&gt;.)&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F31kwzdfckzsko0c8q58i.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F31kwzdfckzsko0c8q58i.png" alt="Level 14: ps aux finds the miner, kill is ignored, kill -9 stops it" width="799" height="395"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Try it
&lt;/h2&gt;

&lt;p&gt;👉 &lt;strong&gt;&lt;a href="https://dockerlinux.com/?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=world" rel="noopener noreferrer"&gt;dockerlinux.com&lt;/a&gt;&lt;/strong&gt;: 17 levels, free, in English and Portuguese. The World needs a free account (email + one-time code); every free level works without one.&lt;/p&gt;

&lt;p&gt;Two islands are still in the fog. If you were building a Linux/DevOps learning game, what would you put there?&lt;/p&gt;

</description>
      <category>vue</category>
      <category>javascript</category>
      <category>gamedev</category>
      <category>linux</category>
    </item>
    <item>
      <title>5 terminal facts that sound fake (but aren't)</title>
      <dc:creator>Dockerlinux</dc:creator>
      <pubDate>Tue, 06 Oct 2026 14:01:13 +0000</pubDate>
      <link>https://dev.to/dockerlinux/5-terminal-facts-that-sound-fake-but-arent-56eo</link>
      <guid>https://dev.to/dockerlinux/5-terminal-facts-that-sound-fake-but-arent-56eo</guid>
      <description>&lt;p&gt;A bit of terminal trivia for your next coffee break. All five are true, I promise.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. 'grep' is a sentence, not a word.
&lt;/h2&gt;

&lt;p&gt;Before grep existed, you'd search a file in the &lt;code&gt;ed&lt;/code&gt; editor with:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;g/re/p
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;g&lt;/strong&gt;lobal · &lt;strong&gt;r&lt;/strong&gt;egular &lt;strong&gt;e&lt;/strong&gt;xpression · &lt;strong&gt;p&lt;/strong&gt;rint. Ken Thompson turned that one command into its own program, and the name stuck.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. Linux time has an expiry date
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="nv"&gt;$ &lt;/span&gt;&lt;span class="nb"&gt;date&lt;/span&gt; &lt;span class="nt"&gt;-u&lt;/span&gt; &lt;span class="nt"&gt;-d&lt;/span&gt; @2147483647
Tue Jan 19 03:14:07 UTC 2038
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;code&gt;2147483647&lt;/code&gt; is the biggest number a signed 32-bit integer can hold. Systems that still count seconds since 1970 in 32 bits overflow one second later. 64-bit time counters are good for roughly 292 billion years, so update the old stuff and relax.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. Daemons are named after a physics demon
&lt;/h2&gt;

&lt;p&gt;&lt;code&gt;sshd&lt;/code&gt;, &lt;code&gt;dockerd&lt;/code&gt;, &lt;code&gt;containerd&lt;/code&gt;: the trailing &lt;em&gt;d&lt;/em&gt; is for &lt;strong&gt;daemon&lt;/strong&gt;. In the 1960s, programmers at MIT borrowed the word from &lt;em&gt;Maxwell's demon&lt;/em&gt;, a thought experiment about a tiny being that quietly sorts molecules. A background helper nobody sees: a perfect name for a process.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="nv"&gt;$ &lt;/span&gt;ps &lt;span class="nt"&gt;-e&lt;/span&gt; | &lt;span class="nb"&gt;grep&lt;/span&gt; &lt;span class="s2"&gt;"d$"&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  4. Tux exists because of a penguin bite
&lt;/h2&gt;

&lt;p&gt;Linus Torvalds likes to tell how a penguin "bit" him at a zoo in Australia. When Linux needed a mascot a few years later, it was going to be a penguin.&lt;/p&gt;

&lt;h2&gt;
  
  
  5. Docker was revealed in a 5-minute talk
&lt;/h2&gt;

&lt;p&gt;Docker was first shown to the world in a &lt;strong&gt;lightning talk at PyCon 2013&lt;/strong&gt;. Five minutes. Today, a big part of the internet runs in containers.&lt;/p&gt;

&lt;h2&gt;
  
  
  Bonus: &lt;code&gt;sl&lt;/code&gt;
&lt;/h2&gt;

&lt;p&gt;Type &lt;code&gt;sl&lt;/code&gt; instead of &lt;code&gt;ls&lt;/code&gt; on a machine with the &lt;code&gt;sl&lt;/code&gt; package installed and a steam locomotive crosses your terminal. It's a real program, made to punish that exact typo. 🚂&lt;/p&gt;

&lt;p&gt;(It also works in &lt;a href="https://dockerlinux.com/?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=facts" rel="noopener noreferrer"&gt;DockerLinux&lt;/a&gt;, my free browser game for learning Linux and Docker, along with a few other easter eggs.)&lt;/p&gt;




&lt;p&gt;&lt;strong&gt;Your turn:&lt;/strong&gt; what's the strangest true fact you know about Linux, Unix or Docker? Best one in the comments might end up in the game. 👇&lt;/p&gt;

</description>
      <category>linux</category>
      <category>docker</category>
      <category>devops</category>
      <category>ai</category>
    </item>
    <item>
      <title>We translated our terminal game into Portuguese. Except the terminal.</title>
      <dc:creator>Dockerlinux</dc:creator>
      <pubDate>Sun, 04 Oct 2026 12:00:00 +0000</pubDate>
      <link>https://dev.to/dockerlinux/we-translated-our-terminal-game-into-portuguese-except-the-terminal-2e2f</link>
      <guid>https://dev.to/dockerlinux/we-translated-our-terminal-game-into-portuguese-except-the-terminal-2e2f</guid>
      <description>&lt;p&gt;&lt;a href="https://dockerlinux.com/?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=i18n" rel="noopener noreferrer"&gt;DockerLinux&lt;/a&gt; is a free game for learning Linux and Docker: a simulated terminal in the browser, 10 levels of missions, on-call "boss levels" where a pretend production server is broken and you have to fix it.&lt;/p&gt;

&lt;p&gt;A lot of players are Brazilian, so this week it got its first second language: &lt;strong&gt;Brazilian Portuguese&lt;/strong&gt;. The interesting part wasn't what we translated. It was what we didn't.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Ff2ouk5bzeyyk0yim37wy.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Ff2ouk5bzeyyk0yim37wy.png" alt="DockerLinux in Portuguese" width="800" height="1000"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  The rule: translate everything &lt;em&gt;around&lt;/em&gt; the terminal, never the terminal
&lt;/h2&gt;

&lt;p&gt;Missions, hints, the lesson after each task, quizzes, buttons, dialogs, the achievements window: all in Portuguese.&lt;/p&gt;

&lt;p&gt;The commands and everything they print: &lt;strong&gt;still English, word for word.&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;root@docker-lab:~/app# docker run -d --name web ngnix
Unable to find image 'ngnix:latest' locally
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;That error is the same on a real machine, in São Paulo or in London. If the game translated it, a learner would meet an unfamiliar message the first time something breaks for real, which is exactly when they need it to be familiar. So the terminal stays a real terminal, and the game explains it in your language around it. The welcome text even says so, in Portuguese: commands and terminal output stay in English, like on a real server.&lt;/p&gt;

&lt;h2&gt;
  
  
  How it's wired
&lt;/h2&gt;

&lt;p&gt;A tiny i18n layer, no library:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Keys with an English fallback.&lt;/strong&gt; Every text has a key; a missing Portuguese text falls back to English, so nothing is ever blank.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Lazy-loaded languages.&lt;/strong&gt; English ships with the app; other languages load only when someone picks them (a dynamic &lt;code&gt;import()&lt;/code&gt;), so English players never download Portuguese text.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Detection, then choice.&lt;/strong&gt; A saved choice wins; otherwise the browser's languages (&lt;code&gt;pt&lt;/code&gt;, &lt;code&gt;pt-PT&lt;/code&gt; → &lt;code&gt;pt-BR&lt;/code&gt;); otherwise English. &lt;code&gt;?lang=pt-BR&lt;/code&gt; works in links.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Plurals done properly.&lt;/strong&gt; Values like &lt;code&gt;{ one, other }&lt;/code&gt; use the browser's plural rules instead of &lt;code&gt;count === 1 ? … : …&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;A test that lists missing keys.&lt;/strong&gt; Adding a language is: copy the English folder, translate, run the tests. A language only appears in the menu once it's marked ready.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Switching language re-translates what's already on screen.&lt;/strong&gt; The lessons already printed in the terminal are re-rendered in the new language, because they're stored as keys, not as text.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  What was harder than expected?
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Tone.&lt;/strong&gt; The game has a character, Prof. Kernel-Panic, with jokes. Jokes don't translate; they get rewritten.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Missions that mention output.&lt;/strong&gt; "Find the line that says &lt;em&gt;Up 2 seconds&lt;/em&gt;" must keep the English output inside a Portuguese sentence.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Length.&lt;/strong&gt; Portuguese is longer. Buttons and the top bar had to cope with ~30% more text.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Your turn
&lt;/h2&gt;

&lt;p&gt;Português is the first. Which language should come next? And if you've localised a developer tool: did you translate the CLI output, or leave it alone?&lt;/p&gt;

&lt;p&gt;👉 &lt;strong&gt;&lt;a href="https://dockerlinux.com/?lang=pt-BR&amp;amp;utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=i18n" rel="noopener noreferrer"&gt;Try it in Portuguese&lt;/a&gt;&lt;/strong&gt; (or English): free, in your browser, no install.&lt;/p&gt;

</description>
      <category>linux</category>
      <category>docker</category>
      <category>vue</category>
      <category>braziliandevs</category>
    </item>
    <item>
      <title>How I turned Docker incidents into game levels (with postmortems)</title>
      <dc:creator>Dockerlinux</dc:creator>
      <pubDate>Sat, 03 Oct 2026 08:01:00 +0000</pubDate>
      <link>https://dev.to/dockerlinux/how-i-turned-docker-incidents-into-game-levels-with-postmortems-jon</link>
      <guid>https://dev.to/dockerlinux/how-i-turned-docker-incidents-into-game-levels-with-postmortems-jon</guid>
      <description>&lt;p&gt;Every tutorial teaches you how to start a container. Almost none teach you what to do when one is down at 3am and people are waiting.&lt;/p&gt;

&lt;p&gt;So I added "boss levels" to &lt;strong&gt;&lt;a href="https://dockerlinux.com/?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=oncall" rel="noopener noreferrer"&gt;DockerLinux&lt;/a&gt;&lt;/strong&gt;, my free game for learning Linux and Docker in a simulated terminal (&lt;a&gt;here's what shipped last time&lt;/a&gt;). Type &lt;code&gt;oncall&lt;/code&gt; and you take the pager.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fqh0ecgt53bfod82lv35j.gif" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fqh0ecgt53bfod82lv35j.gif" alt="A real on-call run: the page, the investigation, the fix and the postmortem" width="420" height="607"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  What it looks like
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;The page.&lt;/strong&gt; A ticket arrives: &lt;code&gt;SEV-1 · INC-101 · The shop is down&lt;/code&gt;. Support says customers can't load the shop; an ops bot mentions the server rebooted at 03:12 for kernel updates.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;You're on prod-01.&lt;/strong&gt; The terminal logs in to a pretend production server where something is broken, and a clock starts (5 minutes for this one). Your own machine is untouched and comes back afterwards.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;You investigate with real commands:&lt;/strong&gt; &lt;code&gt;docker ps -a&lt;/code&gt;, &lt;code&gt;docker logs&lt;/code&gt;, &lt;code&gt;curl&lt;/code&gt;, &lt;code&gt;docker network inspect&lt;/code&gt;. There's a &lt;code&gt;runbook.md&lt;/code&gt; to &lt;code&gt;cat&lt;/code&gt;, and hints if you're stuck (they cost XP).&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;You fix it, any correct way.&lt;/strong&gt; Broken containers crash again on restart, like real ones, so "just restart it" doesn't always work.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The postmortem:&lt;/strong&gt; time, stars, the root cause and the lesson.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fv7guh5acfc1l52o6n9k8.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fv7guh5acfc1l52o6n9k8.png" alt="The page and the postmortem" width="800" height="476"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;There are six incidents, unlocked as you finish the levels that teach what you need:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Incident&lt;/th&gt;
&lt;th&gt;Unlocks after&lt;/th&gt;
&lt;th&gt;You'll need&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;The shop is down&lt;/td&gt;
&lt;td&gt;Level 5 (container lifecycle)&lt;/td&gt;
&lt;td&gt;
&lt;code&gt;docker ps -a&lt;/code&gt;, &lt;code&gt;docker start&lt;/code&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Welcome to nginx?!&lt;/td&gt;
&lt;td&gt;Level 6 (networking &amp;amp; ports)&lt;/td&gt;
&lt;td&gt;reading the PORTS column&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Database unreachable&lt;/td&gt;
&lt;td&gt;Level 6&lt;/td&gt;
&lt;td&gt;
&lt;code&gt;docker network inspect&lt;/code&gt;, &lt;code&gt;docker network connect&lt;/code&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Bad deploy&lt;/td&gt;
&lt;td&gt;Level 8 (building images)&lt;/td&gt;
&lt;td&gt;
&lt;code&gt;docker logs&lt;/code&gt;, rolling back to the previous tag&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;The data vanished&lt;/td&gt;
&lt;td&gt;Level 7 (volumes)&lt;/td&gt;
&lt;td&gt;
&lt;code&gt;docker volume ls&lt;/code&gt;, &lt;code&gt;docker inspect&lt;/code&gt; → Mounts&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Compose half up&lt;/td&gt;
&lt;td&gt;Level 9 (Docker Compose)&lt;/td&gt;
&lt;td&gt;reading Compose's warnings, &lt;code&gt;docker compose logs&lt;/code&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;(Spoiler for the first one only: the server rebooted and &lt;code&gt;shop-web&lt;/code&gt; had no restart policy. &lt;code&gt;docker ps&lt;/code&gt; hides stopped containers; &lt;code&gt;docker ps -a&lt;/code&gt; doesn't.)&lt;/p&gt;

&lt;h2&gt;
  
  
  How it works under the hood
&lt;/h2&gt;

&lt;p&gt;Everything runs in the browser: a small shell, a virtual file system and a simulated Docker daemon (images, containers, ports, networks, volumes). Incidents are just &lt;strong&gt;data&lt;/strong&gt;:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight javascript"&gt;&lt;code&gt;&lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="nl"&gt;id&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;inc_shop_down&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="nx"&gt;code&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;INC-101&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="nx"&gt;title&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;The shop is down&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="nx"&gt;severity&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;SEV-1&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="nx"&gt;requires&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mi"&gt;5&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;                 &lt;span class="c1"&gt;// unlocks when Level 5 is complete&lt;/span&gt;
  &lt;span class="nx"&gt;slaMs&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mi"&gt;5&lt;/span&gt; &lt;span class="o"&gt;*&lt;/span&gt; &lt;span class="nx"&gt;MIN&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;              &lt;span class="c1"&gt;// the time target&lt;/span&gt;
  &lt;span class="nf"&gt;setup&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;machine&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nx"&gt;now&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="cm"&gt;/* break a fresh prod-01: shop-web exited, redis still up */&lt;/span&gt; &lt;span class="p"&gt;},&lt;/span&gt;
  &lt;span class="nx"&gt;resolved&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;m&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;=&amp;gt;&lt;/span&gt; &lt;span class="o"&gt;!!&lt;/span&gt;&lt;span class="nf"&gt;serving&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;m&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;8080&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;shop:1.0&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;),&lt;/span&gt;
  &lt;span class="nx"&gt;hints&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt; &lt;span class="cm"&gt;/* where to look → what it means → the fix */&lt;/span&gt; &lt;span class="p"&gt;],&lt;/span&gt;
  &lt;span class="nx"&gt;solution&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;docker ps -a&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;docker start shop-web&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;curl localhost:8080&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;],&lt;/span&gt;
  &lt;span class="nx"&gt;rootCause&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;…&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nx"&gt;lesson&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;…&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Two decisions made it work:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;&lt;code&gt;resolved()&lt;/code&gt; checks the state, not your commands.&lt;/strong&gt; It asks "is something serving &lt;code&gt;shop:1.0&lt;/code&gt; on port 8080?", not "did they type &lt;code&gt;docker start shop-web&lt;/code&gt;?". So &lt;code&gt;docker start&lt;/code&gt;, &lt;code&gt;docker restart&lt;/code&gt; or a brand-new &lt;code&gt;docker run&lt;/code&gt; with the right port all count, just like in real life.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The &lt;code&gt;solution&lt;/code&gt; is replayed by the tests.&lt;/strong&gt; Every incident ships with a known fix, and the test suite runs it against a fresh broken server, so an incident can never become impossible after an engine change.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Scoring is deliberately simple: &lt;strong&gt;1 star for fixing it, +1 within the time target, +1 without hints.&lt;/strong&gt; Replay for three.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why I think this matters
&lt;/h2&gt;

&lt;p&gt;Most of the job isn't typing &lt;code&gt;docker run&lt;/code&gt;. It's reading &lt;code&gt;docker ps -a&lt;/code&gt; calmly, finding the one log line that matters, and fixing the right thing, under a bit of pressure. A game is a safe place to practise that before it's real.&lt;/p&gt;

&lt;h2&gt;
  
  
  Your turn
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Which real outage should become incident #5?&lt;/strong&gt; A full disk, a DNS surprise, a volume mounted in the wrong place, an OOM-killed container…&lt;/li&gt;
&lt;li&gt;If you run Docker in production: where does the simulation behave differently from the real thing in a way that could mislead someone?&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;👉 &lt;strong&gt;&lt;a href="https://dockerlinux.com/?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=oncall" rel="noopener noreferrer"&gt;dockerlinux.com&lt;/a&gt;&lt;/strong&gt;: free, in your browser, no install. Finish Level 5, then type &lt;code&gt;oncall&lt;/code&gt;.&lt;/p&gt;

</description>
      <category>docker</category>
      <category>devops</category>
      <category>sre</category>
      <category>linux</category>
    </item>
    <item>
      <title>I built "boss levels" for my Linux &amp; Docker game: you're on call and prod is down</title>
      <dc:creator>Dockerlinux</dc:creator>
      <pubDate>Wed, 30 Sep 2026 20:49:20 +0000</pubDate>
      <link>https://dev.to/dockerlinux/i-built-boss-levels-for-my-linux-docker-game-youre-on-call-and-prod-is-down-3p22</link>
      <guid>https://dev.to/dockerlinux/i-built-boss-levels-for-my-linux-docker-game-youre-on-call-and-prod-is-down-3p22</guid>
      <description>&lt;p&gt;Every tutorial teaches you how to start a container. Almost none teach you what to do when one is down at 3am and people are waiting.&lt;/p&gt;

&lt;p&gt;So I added "boss levels" to &lt;strong&gt;&lt;a href="https://dockerlinux.com/?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=oncall" rel="noopener noreferrer"&gt;DockerLinux&lt;/a&gt;&lt;/strong&gt;, my free game for learning Linux and Docker in a simulated terminal (&lt;a&gt;here's what shipped last time&lt;/a&gt;). Type &lt;code&gt;oncall&lt;/code&gt; and you take the pager.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fqdc8b05xnhkmk0x7p490.gif" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fqdc8b05xnhkmk0x7p490.gif" alt="A real on-call run: the page, the investigation, the fix and the postmortem" width="420" height="607"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  What it looks like
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;The page.&lt;/strong&gt; A ticket arrives: &lt;code&gt;SEV-1 · INC-101 · The shop is down&lt;/code&gt;. Support says customers can't load the shop; an ops bot mentions the server rebooted at 03:12 for kernel updates.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;You're on prod-01.&lt;/strong&gt; The terminal logs in to a pretend production server where something is broken, and a clock starts (5 minutes for this one). Your own machine is untouched and comes back afterwards.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;You investigate with real commands:&lt;/strong&gt; &lt;code&gt;docker ps -a&lt;/code&gt;, &lt;code&gt;docker logs&lt;/code&gt;, &lt;code&gt;curl&lt;/code&gt;, &lt;code&gt;docker network inspect&lt;/code&gt;. There's a &lt;code&gt;runbook.md&lt;/code&gt; to &lt;code&gt;cat&lt;/code&gt;, and hints if you're stuck (they cost XP).&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;You fix it, any correct way.&lt;/strong&gt; Broken containers crash again on restart, like real ones, so "just restart it" doesn't always work.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The postmortem:&lt;/strong&gt; time, stars, the root cause and the lesson.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fayjkhin009gbuqugi7o8.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fayjkhin009gbuqugi7o8.png" alt="The page and the postmortem" width="800" height="476"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;There are four incidents, unlocked as you finish the levels that teach what you need:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Incident&lt;/th&gt;
&lt;th&gt;Unlocks after&lt;/th&gt;
&lt;th&gt;You'll need&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;The shop is down&lt;/td&gt;
&lt;td&gt;Level 5 (container lifecycle)&lt;/td&gt;
&lt;td&gt;
&lt;code&gt;docker ps -a&lt;/code&gt;, &lt;code&gt;docker start&lt;/code&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Welcome to nginx?!&lt;/td&gt;
&lt;td&gt;Level 6 (networking &amp;amp; ports)&lt;/td&gt;
&lt;td&gt;reading the PORTS column&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Database unreachable&lt;/td&gt;
&lt;td&gt;Level 6&lt;/td&gt;
&lt;td&gt;
&lt;code&gt;docker network inspect&lt;/code&gt;, &lt;code&gt;docker network connect&lt;/code&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Bad deploy&lt;/td&gt;
&lt;td&gt;Level 8 (building images)&lt;/td&gt;
&lt;td&gt;
&lt;code&gt;docker logs&lt;/code&gt;, rolling back to the previous tag&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;(Spoiler for the first one only: the server rebooted and &lt;code&gt;shop-web&lt;/code&gt; had no restart policy. &lt;code&gt;docker ps&lt;/code&gt; hides stopped containers; &lt;code&gt;docker ps -a&lt;/code&gt; doesn't.)&lt;/p&gt;

&lt;h2&gt;
  
  
  How it works under the hood
&lt;/h2&gt;

&lt;p&gt;Everything runs in the browser: a small shell, a virtual file system and a simulated Docker daemon (images, containers, ports, networks, volumes). Incidents are just &lt;strong&gt;data&lt;/strong&gt;:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight javascript"&gt;&lt;code&gt;&lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="nl"&gt;id&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;inc_shop_down&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="nx"&gt;code&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;INC-101&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="nx"&gt;title&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;The shop is down&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="nx"&gt;severity&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;SEV-1&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="nx"&gt;requires&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mi"&gt;5&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;                 &lt;span class="c1"&gt;// unlocks when Level 5 is complete&lt;/span&gt;
  &lt;span class="nx"&gt;slaMs&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mi"&gt;5&lt;/span&gt; &lt;span class="o"&gt;*&lt;/span&gt; &lt;span class="nx"&gt;MIN&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;              &lt;span class="c1"&gt;// the time target&lt;/span&gt;
  &lt;span class="nf"&gt;setup&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;machine&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nx"&gt;now&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="cm"&gt;/* break a fresh prod-01: shop-web exited, redis still up */&lt;/span&gt; &lt;span class="p"&gt;},&lt;/span&gt;
  &lt;span class="nx"&gt;resolved&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;m&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;=&amp;gt;&lt;/span&gt; &lt;span class="o"&gt;!!&lt;/span&gt;&lt;span class="nf"&gt;serving&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;m&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;8080&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;shop:1.0&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;),&lt;/span&gt;
  &lt;span class="nx"&gt;hints&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt; &lt;span class="cm"&gt;/* where to look → what it means → the fix */&lt;/span&gt; &lt;span class="p"&gt;],&lt;/span&gt;
  &lt;span class="nx"&gt;solution&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;docker ps -a&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;docker start shop-web&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;curl localhost:8080&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;],&lt;/span&gt;
  &lt;span class="nx"&gt;rootCause&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;…&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nx"&gt;lesson&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;…&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Two decisions made it work:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;&lt;code&gt;resolved()&lt;/code&gt; checks the state, not your commands.&lt;/strong&gt; It asks, "is something serving &lt;code&gt;shop:1.0&lt;/code&gt; on port 8080?", not "did they type &lt;code&gt;docker start shop-web&lt;/code&gt;?". So &lt;code&gt;docker start&lt;/code&gt;, &lt;code&gt;docker restart&lt;/code&gt; or a brand-new &lt;code&gt;docker run&lt;/code&gt; with the right port all count, just like in real life.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The &lt;code&gt;solution&lt;/code&gt; is replayed by the tests.&lt;/strong&gt; Every incident ships with a known fix, and the test suite runs it against a fresh broken server, so an incident can never become impossible after an engine change.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Scoring is deliberately simple: &lt;strong&gt;1 star for fixing it, +1 within the time target, +1 without hints.&lt;/strong&gt; Replay for three.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why I think this matters
&lt;/h2&gt;

&lt;p&gt;Most of the job isn't typing &lt;code&gt;docker run&lt;/code&gt;. It's reading &lt;code&gt;docker ps -a&lt;/code&gt; calmly, finding the one log line that matters, and fixing the right thing, under a bit of pressure. A game is a safe place to practise that before it's real.&lt;/p&gt;

&lt;h2&gt;
  
  
  Your turn
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Which real outage should become incident #5?&lt;/strong&gt; A full disk, a DNS surprise, a volume mounted in the wrong place, an OOM-killed container…&lt;/li&gt;
&lt;li&gt;If you run Docker in production: where does the simulation behave differently from the real thing in a way that could mislead someone?&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;👉 &lt;strong&gt;&lt;a href="https://dockerlinux.com/?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=oncall" rel="noopener noreferrer"&gt;dockerlinux.com&lt;/a&gt;&lt;/strong&gt;: free, in your browser, no install. Finish Level 5, then type &lt;code&gt;oncall&lt;/code&gt;.&lt;/p&gt;

</description>
      <category>docker</category>
      <category>devops</category>
      <category>sre</category>
      <category>showdev</category>
    </item>
    <item>
      <title>You asked, and I shipped it: pipes, real error messages and streak freezes in DockerLinux</title>
      <dc:creator>Dockerlinux</dc:creator>
      <pubDate>Tue, 29 Sep 2026 20:52:32 +0000</pubDate>
      <link>https://dev.to/dockerlinux/you-asked-and-i-shipped-it-pipes-real-error-messages-and-streak-freezes-in-dockerlinux-10ob</link>
      <guid>https://dev.to/dockerlinux/you-asked-and-i-shipped-it-pipes-real-error-messages-and-streak-freezes-in-dockerlinux-10ob</guid>
      <description>&lt;p&gt;Earlier this month I posted &lt;strong&gt;&lt;a&gt;DockerLinux&lt;/a&gt;&lt;/strong&gt; here: a free game that teaches Linux and Docker in a simulated terminal in your browser. At the end I asked one question: &lt;em&gt;where does the simulation behave differently from the real thing?&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;You answered, and some requests stood out in the comments, so I built both. Here's what changed and a few extras that came along for the ride.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. Pipes
&lt;/h2&gt;

&lt;p&gt;In the first article I wrote: &lt;em&gt;"Pipes aren't supported yet. They're on the list!"&lt;/em&gt; It didn't stay on the list for long.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fx9h3jum7dixayeng2jiy.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fx9h3jum7dixayeng2jiy.png" alt="Pipes" width="800" height="565"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;There's now a whole new &lt;strong&gt;Level 3, "Pipes: connecting commands"&lt;/strong&gt;, so the course is 10 levels:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="nb"&gt;ls&lt;/span&gt; | &lt;span class="nb"&gt;wc&lt;/span&gt; &lt;span class="nt"&gt;-l&lt;/span&gt;                 &lt;span class="c"&gt;# how many files?&lt;/span&gt;
&lt;span class="nb"&gt;history&lt;/span&gt; | &lt;span class="nb"&gt;grep &lt;/span&gt;docker      &lt;span class="c"&gt;# "what was that command again?"&lt;/span&gt;
docker ps | &lt;span class="nb"&gt;grep &lt;/span&gt;web       &lt;span class="c"&gt;# find one container in a busy list&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;It covers &lt;code&gt;grep&lt;/code&gt;, &lt;code&gt;head&lt;/code&gt;, &lt;code&gt;tail&lt;/code&gt;, &lt;code&gt;sort&lt;/code&gt; and &lt;code&gt;wc&lt;/code&gt;, and your first pipe unlocks the &lt;strong&gt;Plumber&lt;/strong&gt; achievement.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. Error messages, word for word
&lt;/h2&gt;

&lt;p&gt;The other request: make the errors identical to the real ones. That matters more than it sounds, because a beginner learns to &lt;em&gt;read&lt;/em&gt; errors as much as to type commands, and a "close enough" message teaches the wrong thing.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fbia24cxw821p8a9s77lv.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fbia24cxw821p8a9s77lv.png" alt="A real Docker error" width="800" height="414"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Errors now match real bash and Docker &lt;strong&gt;word for word&lt;/strong&gt;, e.g. &lt;code&gt;Unable to find image 'x:latest' locally&lt;/code&gt;. When you meet it on a real machine, you've already seen it.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. Your progress, on any device
&lt;/h2&gt;

&lt;p&gt;Playing still needs no account. But if you want one, it's just your email and a &lt;strong&gt;6-digit code&lt;/strong&gt;, no password. XP, levels, quiz answers, your streak and even the files you created in the simulated machine sync to any computer or phone. You can log out everywhere or delete the account from the menu.&lt;/p&gt;

&lt;h2&gt;
  
  
  4. Streaks that forgive a bad day
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fq2q3niwm4qdh3p73a5uc.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fq2q3niwm4qdh3p73a5uc.png" alt="The streak card" width="800" height="907"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;One command a day keeps your 🔥 streak alive. What I didn't want was one missed day wiping out two weeks of practice, so you now &lt;strong&gt;earn streak freezes&lt;/strong&gt; by finishing levels (you can hold up to 2). Miss a day and a freeze is used for you: ❄️ &lt;em&gt;Streak saved!&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  5. 35 achievements (7 of them secret)
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fzr3hx1p2d1pfdaw0asrm.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fzr3hx1p2d1pfdaw0asrm.png" alt="Achievements page" width="800" height="635"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;There's a proper achievements page now: badges for getting started, levels, Docker, streaks and inviting friends, progress bars on the locked ones ("43/50"), a "Next up" card and a grid of your practice days over the last 6 months.&lt;/p&gt;

&lt;p&gt;Seven are secret. I'm not saying which. 👀&lt;/p&gt;

&lt;h2&gt;
  
  
  6. And two things just for fun
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Byte&lt;/strong&gt;, a pixel penguin who lives at the bottom of the terminal. He hatches on your first command, grows up as you practise, covers his eyes when you get an error and dances when you level up. Try &lt;code&gt;pet dance&lt;/code&gt; or &lt;code&gt;pet style arctic&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;&lt;code&gt;movie&lt;/code&gt;&lt;/strong&gt;: a ~50-second ASCII film, "OUT OF MEMORY". A container leaks memory, the OOM Killer chases it, and &lt;code&gt;docker update --memory 1g&lt;/code&gt; saves the day. The credits end with the actual lesson: set memory limits (&lt;code&gt;docker run -m 512m&lt;/code&gt;).&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  What's next
&lt;/h2&gt;

&lt;p&gt;The same question as last time, because it worked: &lt;strong&gt;what should I build next?&lt;/strong&gt; On my list are permissions, processes, environment variables and multi-stage builds. Tell me which one you'd want first, or what else confused you.&lt;/p&gt;

&lt;p&gt;And if you know Docker well: where does the simulation still differ from the real thing in a way that would mislead a beginner? Every answer to that has made the game better.&lt;/p&gt;

&lt;p&gt;👉 &lt;strong&gt;&lt;a href="https://dockerlinux.com/?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=update1" rel="noopener noreferrer"&gt;dockerlinux.com&lt;/a&gt;&lt;/strong&gt;: still free, still nothing to install.&lt;/p&gt;

</description>
      <category>docker</category>
      <category>linux</category>
      <category>beginners</category>
      <category>showdev</category>
    </item>
    <item>
      <title>You asked, we shipped it: pipes, real Docker errors and streak freezes</title>
      <dc:creator>Dockerlinux</dc:creator>
      <pubDate>Sun, 27 Sep 2026 18:15:39 +0000</pubDate>
      <link>https://dev.to/dockerlinux/you-asked-we-shipped-it-pipes-real-docker-errors-and-streak-freezes-2o10</link>
      <guid>https://dev.to/dockerlinux/you-asked-we-shipped-it-pipes-real-docker-errors-and-streak-freezes-2o10</guid>
      <description>&lt;p&gt;Most people learn Docker by copying commands into a real machine. It works until something breaks and nobody explains why.&lt;/p&gt;

&lt;p&gt;DockerLinux is a free game that fixes that: a simulated Linux + Docker terminal in the browser, with 10 levels of small missions, from pwd to Docker Compose. Nothing to install, nothing real to break.&lt;/p&gt;

&lt;p&gt;After the launch, developers in the comments asked for two things: pipes and error messages identical to real Docker. Both are live now, plus a few more things:&lt;/p&gt;

&lt;p&gt;🔗 A new level on pipes: ls | wc -l, grep, head, tail, docker ps | grep web&lt;br&gt;
💬 Error messages that match real bash and Docker word for word, so nothing surprises you on a real server&lt;br&gt;
❄️ Daily streaks with freezes: finish a level to earn one, and it covers a day you miss.&lt;br&gt;
🏆 An achievements page with 29 badges (5 are secret), progress bars and a practice-day grid&lt;br&gt;
💾 An optional free account with no password (a 6-digit email code) to continue on any device&lt;/p&gt;

&lt;p&gt;It's aimed at students, junior devs and anyone moving into DevOps or cloud, and it works on a phone too.&lt;/p&gt;

&lt;p&gt;If you know Docker well, we'd love your eye on it: where does the simulation behave differently from the real thing in a way that could mislead a beginner?&lt;/p&gt;

&lt;p&gt;Play for Free: &lt;a href="https://dockerlinux.com/?utm_source=devto&amp;amp;utm_medium=social&amp;amp;utm_campaign=update2" rel="noopener noreferrer"&gt;No account needed to start&lt;/a&gt;&lt;/p&gt;

&lt;h1&gt;
  
  
  Docker #Linux #DevOps #CloudComputing #LearnToCode #CareerDevelopment
&lt;/h1&gt;

</description>
      <category>docker</category>
      <category>learning</category>
      <category>linux</category>
      <category>showdev</category>
    </item>
    <item>
      <title>I built a free game to learn Linux &amp; Docker in your browser 🐳🎮</title>
      <dc:creator>Dockerlinux</dc:creator>
      <pubDate>Thu, 24 Sep 2026 20:49:13 +0000</pubDate>
      <link>https://dev.to/dockerlinux/i-built-a-free-game-to-learn-linux-docker-in-your-browser-2p8j</link>
      <guid>https://dev.to/dockerlinux/i-built-a-free-game-to-learn-linux-docker-in-your-browser-2p8j</guid>
      <description>&lt;p&gt;Most people learn Docker by pasting commands from a tutorial into a real machine. It works, right up until it doesn't, and then the terminal feels like a minefield.&lt;/p&gt;

&lt;p&gt;I wanted somewhere beginners could type the real commands, get things wrong and get instant feedback, with nothing to install and nothing real to break. So I built &lt;strong&gt;&lt;a href="https://dockerlinux.com/?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=launch" rel="noopener noreferrer"&gt;DockerLinux&lt;/a&gt;&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fk17b6tjo1b86ditskcno.gif" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fk17b6tjo1b86ditskcno.gif" alt=" " width="360" height="640"&gt;&lt;/a&gt;&lt;/p&gt;


&lt;div&gt;
    &lt;iframe src="https://www.youtube.com/embed/sYn8gdEsqNI" width="315" height="560"&gt;
    &lt;/iframe&gt;
  &lt;/div&gt;


&lt;h2&gt;
  
  
  What it is
&lt;/h2&gt;

&lt;p&gt;A simulated Linux machine with Docker, in a browser tab, wrapped in a small game:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Missions and XP&lt;/strong&gt;: each level is a checklist of small tasks. Finish them to level up, unlock achievements and, at the end, download a certificate.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;A lesson after every task&lt;/strong&gt;: run &lt;code&gt;pwd&lt;/code&gt; and it tells you what &lt;code&gt;/root/app&lt;/code&gt; actually means. Run &lt;code&gt;docker run -d&lt;/code&gt; and it explains what "detached" is.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;A quiz at the end of each level&lt;/strong&gt;, and your progress is saved in your browser.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Works on phones too&lt;/strong&gt;, with on-screen Tab/↑/↓ keys.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  9 levels, from zero to Compose
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fifl3h62h638ttdsrmbjt.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fifl3h62h638ttdsrmbjt.png" alt=" " width="800" height="1000"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;It starts with the absolute basics (&lt;code&gt;pwd&lt;/code&gt;, &lt;code&gt;ls&lt;/code&gt;, &lt;code&gt;cd&lt;/code&gt;, hidden files) and ends with building your own image and running a multi-container app with &lt;code&gt;docker compose up&lt;/code&gt;. The last level is a sandbox where you can play freely.&lt;/p&gt;

&lt;h2&gt;
  
  
  Stuck? Never for long
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fievppn4lpy2wtx26vvcb.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fievppn4lpy2wtx26vvcb.png" alt=" " width="800" height="1000"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Hints come in three steps: &lt;strong&gt;the idea&lt;/strong&gt;, then &lt;strong&gt;the syntax&lt;/strong&gt;, then &lt;strong&gt;the answer&lt;/strong&gt;. Each step costs a bit of XP, so you're nudged to think first, but you're never left stuck.&lt;/p&gt;

&lt;h2&gt;
  
  
  How it works under the hood
&lt;/h2&gt;

&lt;p&gt;There's no real VM or container behind it. It's all JavaScript in your browser:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;A tiny shell&lt;/strong&gt;: a tokenizer that understands quotes, &lt;code&gt;&amp;amp;&amp;amp;&lt;/code&gt;, &lt;code&gt;||&lt;/code&gt;, &lt;code&gt;;&lt;/code&gt; and &lt;code&gt;&amp;gt;&lt;/code&gt; / &lt;code&gt;&amp;gt;&amp;gt;&lt;/code&gt; redirects, plus an argument parser for flags like &lt;code&gt;-d&lt;/code&gt;, &lt;code&gt;--name web-server&lt;/code&gt; and &lt;code&gt;-p 8080:80&lt;/code&gt;. (Pipes aren't supported yet. They're on the list!)&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;A virtual file system&lt;/strong&gt; with real paths, so &lt;code&gt;cd ..&lt;/code&gt;, &lt;code&gt;ls -la&lt;/code&gt;, &lt;code&gt;cat&lt;/code&gt;, &lt;code&gt;mkdir&lt;/code&gt; and &lt;code&gt;echo "hi" &amp;gt; file.txt&lt;/code&gt; behave the way you'd expect.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;A simulated Docker daemon&lt;/strong&gt;: images you can pull, a container lifecycle (&lt;code&gt;run&lt;/code&gt;, &lt;code&gt;stop&lt;/code&gt;, &lt;code&gt;start&lt;/code&gt;, &lt;code&gt;rm&lt;/code&gt;, &lt;code&gt;logs&lt;/code&gt;), name and port conflicts, volumes, networks, &lt;code&gt;docker build&lt;/code&gt; that reads the Dockerfile in the virtual file system, and &lt;code&gt;docker compose up&lt;/code&gt; that reads the YAML. &lt;code&gt;curl localhost:8080&lt;/code&gt; even answers once a container publishes that port.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Levels are data&lt;/strong&gt;: each task has a &lt;code&gt;check(ctx)&lt;/code&gt; function that runs after every successful command, so the game reacts to what you actually did rather than to one exact string.
&lt;/li&gt;
&lt;/ul&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight javascript"&gt;&lt;code&gt;&lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="nl"&gt;desc&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;Start an Nginx web server container in the background, named 'web-server'&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="nx"&gt;hints&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;`docker run` creates and starts a container...&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;docker run -d --name &amp;lt;name&amp;gt; &amp;lt;image&amp;gt;&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;],&lt;/span&gt;
  &lt;span class="nx"&gt;hint&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;docker run -d --name web-server nginx&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="nx"&gt;check&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;ctx&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;=&amp;gt;&lt;/span&gt; &lt;span class="nf"&gt;runningContainer&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;ctx&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;web-server&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;nginx&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;),&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The UI is &lt;strong&gt;Vue 3 + Vite + Tailwind&lt;/strong&gt;. Terminal output is rendered as structured segments (no &lt;code&gt;v-html&lt;/code&gt; anywhere), which made it possible to ship a strict Content Security Policy. It's hosted on &lt;strong&gt;Cloudflare Workers&lt;/strong&gt;, with &lt;strong&gt;D1&lt;/strong&gt; (SQLite) for the optional newsletter signup.&lt;/p&gt;

&lt;h2&gt;
  
  
  Try it
&lt;/h2&gt;

&lt;p&gt;👉 &lt;strong&gt;&lt;a href="https://dockerlinux.com/?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=launch" rel="noopener noreferrer"&gt;dockerlinux.com&lt;/a&gt;&lt;/strong&gt;: free, no account needed.&lt;/p&gt;

&lt;p&gt;I'd love feedback, especially from people who are just starting out:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;What confused you?&lt;/li&gt;
&lt;li&gt;Which command did you expect to work that didn't?&lt;/li&gt;
&lt;li&gt;What should the next levels cover: permissions, pipes and &lt;code&gt;grep&lt;/code&gt;, processes, environment variables, and multi-stage builds?&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;And if you're experienced with Docker: where does the simulation behave differently from the real thing in a way that could mislead a beginner? That's the feedback I value most. 🙏&lt;/p&gt;

</description>
      <category>docker</category>
      <category>linux</category>
      <category>beginners</category>
      <category>showdev</category>
    </item>
  </channel>
</rss>
