Running Your First Docker Container on Unraid

What a Container Is (an App in a Tidy Box)

A "container" is simply an app bundled up with everything it needs to run, sealed in its own tidy box. That box keeps the app separate from the rest of your server.

Picture a lunchbox. Everything the meal needs is inside it, and it does not spill onto the rest of the fridge. A container is like that for an app - it carries its own bits and pieces, and it does not make a mess of your server.

• The app cannot rummage through the whole server - only what you allow.
• Removing the app is clean - the box goes and takes its clutter with it.
• Many apps can run side by side without stepping on each other.

Why Containers Keep Things Clean

The big benefit of containers is tidiness. Because each app lives in its own box, your server stays orderly no matter how many apps you run.

This is why Unraid leans on containers for apps. It keeps a home server pleasant to manage, even for someone who never wants to touch a command line.

• No tangles - one app's needs do not clash with another's.
• Easy removal - delete the box and the app is gone, no leftovers scattered around.
• Easy to redo - if an app acts up, you can remove and reinstall it fresh.
• Safer - a misbehaving app is boxed in, not loose on your whole system.

Installing One From Community Applications

You get containers from the Apps tab, which is powered by Community Applications - Unraid's app store. If you have that tab, you are ready to go.

Clicking Install opens the template - the pre-filled form we will walk through next. Nothing is running yet at this point. You get to review the settings before anything starts.

• Open your Unraid page in a web browser and sign in.
• Click the "Apps" tab to open the app store.
• Search for the app you want, by name or by what it does.
• Pick a result with a trusted, well-known author and lots of installs.
• Click the app, read its info, then click "Install."

The Template Fields, Explained

When you click Install, you meet the template - a form with the app's settings filled in. Two of the top fields are worth understanding: the name and the repository.

The "Name" is just a label for you - handy when you have several apps. The "Repository" is the address the app comes from; the template sets it correctly, so you should not change it. If you do, the app may not install.

Port Mappings, in Plain Words

A "port" is like a numbered door on your server that an app answers on. A port mapping simply connects a door on your server to the app's own door inside its box.

Think of your server as a building with many numbered doors. When you visit an app's web page, you knock on a specific door number, and the app inside answers. The template already picks a sensible door for you.

• The template fills in a port number that usually just works.
• You only change it if two apps want the same door - then you give one a different number.
• You will use this number to open the app's page in your browser.

Path Mappings - Host Folder vs. the App's Folder

A "path" is just a folder. A path mapping links a folder on your server to a folder the app sees inside its box. This is how an app reaches your files - only the ones you point it at.

So if a media app wants a folder called "/movies" inside its box, you map that to your real Movies share on the server. The app then sees your movies, and nothing else you did not share.

• Host path - a real folder on your Unraid server, like your Movies share.
• Container path - the folder name the app uses inside its own box.
• The mapping says "when the app looks in its folder, show it this real folder."

The appdata Path (Where Settings Are Kept)

One special folder shows up in almost every template: appdata. This is where a container keeps its own settings and small working files. It is worth understanding because it is worth backing up.

When you set up an app - its preferences, its accounts, its little bits of memory - all of that lives in the app's appdata folder. If appdata is safe, your setup is safe, even if you remove and reinstall the app.

• The template usually points appdata at a shared "appdata" folder for you.
• Keeping all apps' settings under one appdata area makes it easy to back up.
• Backing up appdata means you can restore your apps without starting over.

Environment Variables, Simply

Some templates have fields called "environment variables." Do not let the name scare you - they are just extra settings the app reads when it starts, like filling in a couple of blanks on a form.

The template fills in most of these for you. When one needs your input, it is usually labeled clearly, like "set your time zone." You just type in the value it asks for and move on.

• A time zone, so the app shows the right clock.
• A username or password to set up the app the first time.
• A simple on/off choice for a feature.

Starting the Container

Once the template looks right, starting the app is a single click. This downloads the app and sets it running for the first time.

Your first start takes the longest because it downloads the app. After that, starting and stopping are quick. The app now appears on your Docker tab, ready to use.

• Scroll down and give the template one last look.
• Confirm any folder mappings point at the right places.
• Click "Apply" at the bottom.
• Watch the progress as it downloads and sets up - this can take a minute or two.
• When it says "Done," close the window.

Opening the App's WebUI Link

Most containers are apps you use through a web page, called the "WebUI." Unraid gives you a one-click link straight to it, so you do not have to remember any addresses.

That WebUI page is the app itself. Bookmark it if you use it often. Behind the scenes it uses the port we talked about earlier, but Unraid handles that for you with the WebUI link.

• Go to the Docker tab and find your app in the list.
• Click the app's icon to open its menu.
• Choose "WebUI."
• The app's page opens in a new browser tab - this is where you use the app.

Checking the Container's Logs

A "log" is the app's running diary - a list of what it is doing and any problems it hits. When something is not working, the log is the first place to look.

You do not need to understand every line. Often the log will spell out the problem in near-plain English, like a folder it cannot find or a password that is missing. That is usually enough to point you at the fix.

• On the Docker tab, click the app's icon.
• Choose "Logs" from the menu.
• A window opens showing the app's messages, newest at the bottom.
• Look for lines that say "error" or "warning" for clues.

Updating a Container

Apps get updates for new features and security fixes. Unraid tells you when one is ready and makes updating a click or two. It is a good habit to keep up with.

You do not need to check every day. Glancing at the Docker tab now and then and updating when you see the note keeps everything current with almost no effort.

• On the Docker tab, apps with an update are marked clearly.
• Click the app and choose the update option, or use "update all."
• The app briefly restarts as it updates - this is quick.
• Your settings in appdata carry over, so nothing is lost.

Stopping and Removing One

You can pause an app by stopping it, or get rid of it entirely by removing it. Both are simple and safe, and they only affect that one app.

To do any of these, click the app's icon on the Docker tab and pick the option. Removing an app usually leaves its appdata settings folder behind, so if you reinstall later, your setup can come back.

A Good, Simple First App to Try

For your very first container, pick something simple and useful with a friendly web page. A dashboard or a file browser is a gentle, low-risk place to start.

The idea is to choose something where a mistake costs nothing and success is obvious. Once you have installed it, opened its WebUI, and clicked around, the whole process will feel far less mysterious.

• A dashboard - a tidy home page with links to your other apps and server info.
• A file browser - a simple web page to view files on your server.
• A notes or bookmarks app - small, self-contained, and easy to grasp.

Making a Container Start Automatically

You will usually want your apps to come back on their own after the server restarts. Unraid does this with a simple "autostart" switch.

With autostart on, the app comes back by itself after a reboot or a power blip - you do not have to remember to turn it on. Most people leave their everyday apps set to autostart.

• Go to the Docker tab.
• Find the "Autostart" switch next to your app.
• Flip it on for apps you want running all the time.
• Leave it off for apps you only use now and then.

How Much Power and Memory a Container Uses

A fair question: does running apps bog down my server? Usually not much. Most simple containers are light, and Unraid shows you exactly how much each one uses.

If your server ever feels sluggish, the Docker tab tells you which app is working hardest. Most of the time, though, a handful of everyday apps sit quietly using next to nothing.

• Small apps - dashboards, file browsers - use very little power or memory.
• Heavier apps - media servers converting video - use more, but only when busy.
• The Docker tab shows each app's memory and processor use at a glance.
• You can run several light apps comfortably on a modest server.

Basic Troubleshooting

When a container will not behave, a short checklist solves most problems. Work through these calmly before assuming anything is seriously wrong.

If none of that helps, search the app's name plus "Unraid" or visit its support thread. Chances are someone has hit the same snag and the fix is written down.

• Is the app started? Check the Docker tab - a stopped app does nothing.
• Read the logs - they usually name the problem in near-plain words.
• Check your folder mappings - a wrong or missing folder is a common cause.
• Try stopping and starting the app again - this clears many glitches.
• Make sure any required setting, like a password, was actually filled in.

Good Habits Going Forward

A few simple habits keep your containers happy for the long run. None of these are hard - they just save you headaches down the road.

Stick to these and your server stays tidy, safe, and easy to manage. A calm, well-kept server is a joy to own - and it is well within your reach.

• Back up appdata - it holds every app's settings.
• Add apps slowly - one at a time, comfortable with each before the next.
• Update at quiet moments - keep apps current without interrupting anyone.
• Keep apps on your local network - never expose ports to the internet.
• Note what you set up - a short list of your apps and their folders helps later.

What's in the 27-page PDF

• What a container actually is, and why it keeps things clean
• The template fields explained - name, ports, folders, and more
• Starting your first app and opening its web page
• Checking logs, updating, and stopping a container
• A friendly first app to try, and how to start it automatically
• Basic troubleshooting and good habits going forward

Why I wrote this

I write these as printable handouts because a guide you can keep in a drawer beats a web page you have to find again. No jargon, no judgment, no rushing. If you'd rather have someone sit beside you and go through it together, that's a flat $99 first visit with the 30-day follow-up included — serving Portage County from Atwater, Ohio. — Bill