LocalNode
How it worksDemoAppsPricingFAQShop now
← All guides
Home/Community/Upgrading a Docker Container in Portainer

Upgrading a Docker Container in Portainer

Advanced
Beginner
5 min read
Published: May 7, 2026

Was this helpful?

Help us improve our community guides.

In this guide

  • Overview
  • Step 1: Re-pulling the image
  • Step 2: Recreating the container
  • Step 3: Cleaning up old images

Need direct help?

LocalNode Care Plan members get priority remote support.

Email Support →

More in Advanced

Adding External Storage to Your Localnode

Adding External Storage to Your Localnode — Step-by-step guide for your LocalNode.

5 min read

Adding Smart Home Devices to Home Assistant

Adding Smart Home Devices to Home Assistant — Step-by-step guide for your LocalNode.

5 min read

Backing Up Your Entire Localnode Configuration

Backing Up Your Entire Localnode Configuration — Step-by-step guide for your LocalNode.

5 min read
LocalNode

Plug-and-play home server. Your data, your hardware, your rules.

Product

How it worksDemoAppsCommunityPricingFAQ

Support

ContactShipping & ReturnsTrack Order

Legal

Privacy PolicyTerms of ServiceShipping Policy
© 2026 LocalNode. Built for people who value their privacy.Denton, TX · hello@localnode.tech

⚠️ Administrative Tool — LocalNode generally updates apps automatically. Only do this if an update is stuck.

Sometimes an app (like Home Assistant or Nextcloud) releases a major new version and you want it immediately, rather than waiting for the automated update script. You can manually force a Docker container update using Portainer.

Overview

Docker containers are meant to be disposable. To update an app, you don't run an updater inside the app. Instead, you download the newest container "image", delete the old container, and create a brand new container using the new image. Because your configuration files are stored safely outside the container, no data is lost.

Step 1: Re-pulling the image

  1. Log into Portainer from your LocalNode dashboard.
  2. Click your Local environment.
  3. Click Containers in the sidebar.
  4. Click on the specific container you want to update (e.g., jellyfin). Do NOT check the box next to it; click the actual name.
Portainer architectural diagram; container detail actions such as Recreate live under each container view.
Portainer CE diagram (portainer/portainer, zlib license).

Step 2: Recreating the container

This is a two-click process that safely rebuilds the app.

  1. At the top of the container details page, click the Recreate button.
  2. A confirmation modal will appear.
  3. CRITICAL: Turn the toggle ON that says "Pull latest image". If you do not turn this on, it will just rebuild the container using the old version.
  4. Click Recreate.

The screen may freeze for 30–60 seconds. Behind the scenes, Portainer is stopping the app, downloading the new files from Docker Hub, deleting the old app, and starting the new one. When it finishes, you will be redirected to the container list, and the app will be running the latest version.

💡 Tip: If the app fails to start after an update, you can always revert. You would simply change the "Image" field to point to the specific older version (e.g., jellyfin/jellyfin:10.8.0) and recreate it again.

Step 3: Cleaning up old images

When you pull a new image, the old image (which is often 1GB+) is left on your hard drive in case you need to roll back. Over a year, this can consume a lot of space.

  1. In the Portainer left sidebar, click Images.
  2. Look for images tagged as <none>. These are the orphaned old versions.
  3. Check the boxes next to them.
  4. Click Remove at the top.

Need help? Email hello@localnode.tech or visit localnode.tech/contact.