On a Docker Standalone host, the safe Portainer update sequence is back up the Portainer data, stop and remove only the Portainer container, pull the image for the edition you use, and recreate the container with the same persistent data mount and connection settings. Your stacks and other application containers remain in place because removing the Portainer container does not remove the Docker resources it manages.
Antihost offers VPS plans with one-click Docker, NVMe storage and a 14-day free trial.
The process is different for Docker Swarm, where Portainer runs as services and must be updated from a manager node. Portainer Agents should also use a version that matches the Portainer Server.
As an Amazon Associate I earn from qualifying purchases.
Recommended Free Tools
Before you update: identify what is running
Do not start by deleting a container until you know how the current installation was deployed. Record the details that make the replacement equivalent to the old one:
- Whether the server uses Community Edition (CE) or Business Edition (BE).
- The current Portainer container name.
- The image tag currently in use, including whether it is an LTS tag or a pinned version.
- Published ports, especially 9443, 9000 and 8000.
- The persistent volume or bind mount that contains Portainer’s data, normally
portainer_data:/data. - The Docker socket mount, normally
/var/run/docker.sock:/var/run/docker.sock. - Certificate options, environment variables, custom Agent secrets and any additional mounts.
- Whether an Agent, Edge Agent or Swarm service is part of the deployment.
The replacement container must use the same data location. If you omit that mount, Portainer starts with an empty database and will appear to have lost its environments, users and stacks even though the old data still exists elsewhere.
#1 Best Overall
- BLUE LIGHT BLOCKING GLASSES: Our blue light glasses for women boast UV400 protection, blocking harmful blue rays from computer screens. With these bluelight glasses women, you can enjoy gaming, reading, or watching TV with no worries of eye strain.
- EYE RELIEF: Our blue light glasses are engineered to reduce blurry vision or strain caused by prolonged screen time. These womens blue light glasses aid in better sleep by preventing blue light from disrupting your natural sleep cycle, helping you fall asleep faster and enjoy a more restful night's sleep, making them the perfect christmas present.
- COMFORTABLE: Crafted from durable material, our trendy blue light glasses for woman or blue light glasses men ensure long-lasting comfort. The high-transmittance lenses accessories, gamer gifts for men, help keep your eyes relaxed. Perfect stocking stuffers, gifts for gamers men, christmas gifts for men, halloween costumes.
- LIGHTWEIGHT: These clear blue light glasses feature a lightweight frame, meaning they’ll stay comfy for long-term wear. Perfect as blue blockers glasses for women or mens blue light glasses, these non-prescription fake glasses for men can be worn throughout the day. The blue light blocking glasses women feature polycarbonate HD lenses, which are anti-reflective and restore true color.
- WORRY-FREE PURCHASE: If you experience any issues, our support team is ready to assist you quickly. These are the perfect costume glasses for cosplay dressing up.
Back up Portainer before changing the container
Portainer recommends backing up the current configuration before every update. Treat this as a prerequisite, not an optional cleanup step. The backup should include the persistent Portainer data, because that data contains the database, users, endpoint definitions, settings and stack metadata.
Use the backup procedure appropriate to your storage layout and verify that the resulting archive or snapshot can be read. A volume-level backup is particularly important before any database-changing operation, such as an edition rollback. Keep the backup separate from the Docker host if a host failure is part of your threat model.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Do not confuse a Portainer configuration backup with a backup of the application data used by your stacks. Updating Portainer does not back up databases, uploads or bind-mounted files belonging to those applications; protect those separately.
Update Portainer on Docker Standalone
The following sequence applies when Portainer is a regular Docker container managed on one host. It preserves the existing Portainer database by reusing the same persistent data volume.
Rank #2
- WINDEX GAMING WIPES: effortlessly clean all your gaming gear and gaming electronics in one easy step with our new Windex Gaming Wipes
- AMMONIA FREE: our ammonia-free formula is safe to use on all of your favorite gaming equipment like consoles, headsets, controllers, screens, keyboards, and more
- PRE-MOISTENED WIPES: each wipe instantly removes dust, dirt, and stubborn smudges and fingerprints leaving a streak-free shine
- ANTI-STATIC: great for cleaning and wiping down your gaming gear and electronics leaving behind no visible residue
- COMPACT RESEALABLE PACKAGE: store your pack of Windex Gaming Wipes anywhere in your home for whenever a quick and easy wipedown is needed
1. Choose the correct image
Community Edition and Business Edition use different repositories:
| Edition | Image for the documented LTS update | Use when |
|---|---|---|
| Community Edition | portainer/portainer-ce:lts |
Your existing installation is CE. |
| Business Edition | portainer/portainer-ee:lts |
Your existing installation is BE. |
Do not replace a BE container with the CE image, or the reverse, as a routine update. Edition changes are a separate migration with separate rollback instructions. If you require reproducible deployments, use a specific version tag instead of moving automatically with lts; record the exact tag so you can recreate the same release later.
Free tools Windows power users keep installed
One-click scans. No signup required.
2. Stop and remove only the old Portainer container
With a container named portainer, run:
docker stop portainer
docker rm portainerThese commands remove the container object, not the persistent portainer_data volume and not the other application containers on the host. If your container has a different name, substitute that name. Never add volume-removal options unless you deliberately intend to erase Portainer’s data.
3. Pull the matching image
Pull the image that matches the edition you recorded:
Rank #3
- Ergonomic & Adjustable Design: Fight "text neck" and improve your posture. Designed for comfort, it offers an adjustable height (7.1in-8.5in) (1.4in adjustable range) and angle (5°-85°) Please note: cell phone stand is only 9 inches tall—the length of a standard pencil
- Without blocking subtitles Perfect for office desk Tiktok Face Time Zoom video—this is the ultimate kitchen desk essential for phones! Perfect viewing experience while reducing neck back strain, A must-have for gamers streamers desk, and anyone who values both style and support!
- Sleek & Stable Design fits Otterbox Case: Say goodbye to bent cables, tangles, and tip-overs! LISEN’s stylish adjustable desk phone holder features a built-in charging hole and smart cable management, keeping your phone secure and your workspace clutter-free cool gadgets for men
- ANTI-SLIP DESIGN free hands: The under 10.00 items easy gadgets back and the bottom of this kitchen essentials for women are fully covered by anti-skid silicone, which LISEN stand up desk decor can provide maximum protection device from any scratches and slides
- Your Perfect Viewing Companion:If your product arrives damaged or breaks within 365 days, reach out to LISEN for a quick and hassle-free solution. Struggling with assembly, like tightening the screw? We’ve got your back! Your experience matters to us. (Product including: phone Holder stand*1, screw*1, hexagon screwdriver*1, specification*1)
docker pull portainer/portainer-ce:lts
# or, for Business Edition
docker pull portainer/portainer-ee:ltsThe pull downloads the image; it does not replace a running container. The new image is used only when you recreate the container.
4. Recreate the container with the same persistent settings
The standard Community Edition deployment is:
docker run -d
-p 8000:8000 -p 9443:9443
--name=portainer --restart=always
-v /var/run/docker.sock:/var/run/docker.sock
-v portainer_data:/data
portainer/portainer-ce:ltsFor Business Edition, replace the final image with portainer/portainer-ee:lts. Keep every deployment-specific option from the old container: custom host ports, certificate flags, environment variables, extra mounts and any Agent-secret setting. A command copied from a generic example is not safe if the original installation used a bind mount instead of portainer_data, a nonstandard container name or custom TLS files.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →5. Sign in and confirm the upgrade
Open https://your-server-address:9443 and sign in. Confirm that your environments, stacks, users and settings are present, then check the displayed Portainer version. Portainer indicates that the update notification should disappear after a successful upgrade.
HTTPS on port 9443 is the current default for CE from version 2.9 and for BE from version 2.10. Port 9000 is optional HTTP compatibility; publish it only if an existing integration requires HTTP. Port 8000 is used for Edge Agent communication and can be omitted when your deployment does not need it. Changing a published port changes how you reach Portainer, but it does not change the internal data path.
Rank #4
- Easy Installation: Our gaming lights have been designed to enhance your entertainment experience. Simply position the led light bar next to your TV or game console to create a game room environment with ease. They come with USB power and a 60 inch cord for direct mounting and mobility
- Audio Syncing & Extensive Mode: The built-in high-sensitivity music sensor allows you to sync the TV led lights to your favorite music. Lights react and move to the beat of music, film and game audio, creating an incredible immersive sound and light experience – and all without the need for an additional hub. You can choose from 64+ patterns, including strobe, illusion, jump, energy, gradient, running, chasing, fluttering mode etc. Each mode can be applied to different scenes
- 64+ Chasing IC+RGB & W Effect: The independent control design of IC+RGB and white all-in-one multifunctional rgbw led bar lights monitor backlight allows you to easily switch the led lights for desk between IC+RGB and white to enjoy a variety of lighting effects, you can choose white lighting mode with high brightness for better illumination when working, etc. Choose IC+RGB lighting mode when you need to create an entertaining atmosphere for the light show, 16 million colours of Color changing rgb light bar let you dance to the beat and create a dynamic party atmosphere
- Dynamic and Dimmable Lights: 1%-full brightness free brightness adjustment gives you the flexibility to adjust dimmable led light bar for room decorations or a variety of occasions
- USB Powered: USB light bars for room can be powered by powernank, usb charger, TV, Monitor, laptop PC mainframe, making behind TV led lighting bar easy to install in any location.TV led lights are powered by the TV usb interface / PC mainframe, can be turned on/off synchronously with TV / PC
What happens to stacks and application containers?
Removing the Portainer container does not stop or delete the application containers that Portainer manages. Those containers and their Docker volumes remain on the host. Portainer’s own records are retained in the persistent data volume and are read by the replacement container.
There are two important boundaries:
- If you reuse the correct
/datavolume, the Portainer database is upgraded in place when the replacement starts. - If you delete the data volume, point the replacement at a new empty path or change the Docker endpoint, Portainer may look like a fresh installation even though the applications still run.
After signing in, open a representative stack and confirm that its deployment definition and endpoint are present before making other changes.
Updating the Portainer Agent
Match the Agent version to the Portainer Server version. A mismatched Agent can prevent management operations or produce compatibility errors even when the Server itself starts normally.
Agent-only update sequence
- Identify the Agent container name, image, socket mount, data or configuration mounts and any published ports.
- If the deployment uses a custom
AGENT_SECRET, record the existing value. The replacement Agent must receive the same secret. - Stop and remove the old Agent container without deleting its required volumes.
- Pull the LTS Agent image:
docker pull portainer/agent:lts- Recreate the Agent with the Docker socket, required volume mounts, ports and secret from the original deployment.
- Check the Server’s environment view and confirm that the Agent reconnects and reports healthy.
The exact Agent run command depends on how the endpoint was deployed, so do not substitute a generic mount list for the mounts used by your installation.
Best Value
- Compatible with Wide Screens - To ensure compatibility with the dual monitor mount, your each monitor must meet three conditions at the same time: First, computer screens size range: 13 to 32 inches. Second, screen weight range: 4.4 to 19.8 lbs. Third, the back of the monitor screen must have VESA mounting holes with a pitch of 75x75mm or 100x100mm.
- Regarding the compatibility with desks - Your desk must meet three conditions at the same time: First, desk material: Only wooden desks are recommended, plastic or glass desks cannot be used. Second, desk thickness range: 0.59" - 3.54". Third, the bottom of the desk should not have any cross beams or panels, as this will interfere with installation. We recommend carefully checking that your desk and monitors meets all above conditions before purchasing.
- Dual C-Clamp Hold - Worried your dual monitors might wobble or slip? Our upgraded base uses a larger platform plus a dual C-clamp structure to lock the dual monitor arm firmly to your desk. Each arm safely keeps your screens steady while you type, click and game—no shaking, no sliding, just a clean and secure setup you can trust every day. It also provides Grommet Mounting installation choice, both options ensure stable and secure fixation for your 0.59" - 3.54" desk.
- Full-Motion Adjustment For Comfortable View - Pull the screen closer when you’re deep in a spreadsheet, push it back to watch videos, or rotate to portrait for coding — moving everything smoothly with just one hand. The monitor stand offers +85°/-50° tilt, ±90° swivel and 360° rotation. Raise your monitor up to 15.75″ to support a healthy sitting posture. Whether you’re working from home, gaming through the night, or switching between video calls and documents, getting the screens to your natural line of sight helps relieve neck, shoulder and back strain so you can stay focused longer with less fatigue.
- Keep Your Desk Organized: By lifting both screens off the desktop, this dual monitor stand opens up valuable space for your keyboard, notebook, docking station or a simple, clutter-free work area. Built-in cable management guides wires along the arms, keeping cords out of sight and out of the way. Enjoy a tidy, modern workstation that looks as good as it feels to use.
Legacy 1.x installations
Portainer warns that a 1.x installation must first move to version 2.0.0 before upgrading to a current release. Do not jump directly from 1.x to the latest image. Make a verified backup, perform the intermediate upgrade, check that the data opens correctly, and then continue with the current supported path.
Docker Swarm uses service updates, not container replacement
A Swarm deployment is not updated with the Standalone docker stop, docker rm and docker run sequence. Run the update from a Swarm manager node and update the Portainer Server and Agent services using Docker service commands or the deployment definition that created them.
Before changing the services:
- Back up the Portainer configuration.
- Confirm the service names, images, published ports, secrets, configs and persistent storage.
- Plan the Server and Agent image changes together so their versions remain matched.
- Check service rollout status and logs after each update.
Because service names and placement constraints differ between Swarm installations, use the service definitions already deployed rather than copying the Standalone container command. A manager node is required to issue the service update.
Choosing an update tag: LTS or a pinned version
| Choice | Advantages | Trade-off |
|---|---|---|
| LTS tag | Simple ongoing maintenance and the documented current long-term-support image. | A later pull can select a newer LTS release, so the exact version is not fixed. |
| Pinned version tag | Repeatable recreations, controlled change windows and easier rollback to the known image. | You must track releases and deliberately change the tag when upgrading. |
Whichever approach you choose, record the image tag, backup date and deployment command. That record turns a future recovery into a repeatable operation rather than a reconstruction exercise.
Rollback and edition migration require extra care
A normal update and a rollback are not equivalent. Portainer maintains separate upgrade and rollback guidance because database changes made by a newer release may not be reversible by simply starting an older image.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsBefore a database-changing rollback, back up the Portainer data volume. The documented Business-to-Community path stops the instance, creates a tar backup of /data, runs the prescribed database rollback command, and redeploys Community Edition using the existing data. Follow that procedure exactly for the release and edition involved; do not treat changing portainer-ee to portainer-ce as an ordinary image swap.
If the new container starts but the database cannot be opened, stop further migrations, preserve the current data, and restore the verified backup or follow Portainer’s rollback documentation for that version. Keeping the old image available is useful, but an old image alone cannot undo a database migration.
Quick Recap
Troubleshooting after the update
| Symptom | Likely cause | What to check |
|---|---|---|
| Portainer shows the first-run setup screen | The replacement container is using a new or incorrect data path. | Compare the old and new /data mount. Recreate it with the original volume or bind mount; do not initialize a new account. |
| The browser cannot connect on 9443 | The port was not published, was changed, or is blocked upstream. | Verify the published port and open https://your-server-address:9443. Check firewall and reverse-proxy rules if applicable. |
| HTTP on port 9000 stopped working | The new command retained only the current HTTPS default. | Add the original -p 9000:9000 mapping only when HTTP compatibility is required, and prefer the HTTPS endpoint for normal access. |
| Edge Agent endpoints are offline | Port 8000 was omitted or changed. | Restore the original 8000 mapping when the deployment uses Edge Agent communication, then verify the Agent address. |
| An Agent reports an incompatibility | Server and Agent versions do not match. | Update the Agent to the corresponding Server release and preserve any custom AGENT_SECRET. |
| Stacks exist on the host but are missing in Portainer | The Portainer database or Docker endpoint differs from the old deployment. | Check the persistent data mount, Docker socket mount and endpoint configuration before redeploying anything. |
| The container exits immediately | A required mount, flag, environment variable or certificate path was omitted. | Compare the replacement command with the original deployment details and inspect the container logs. |
Standalone versus Swarm: which procedure applies?
| Deployment | Update mechanism | Where to run it | Key requirement |
|---|---|---|---|
| Docker Standalone Server | Stop and remove the Portainer container, pull the matching image, recreate it. | The Docker host running Portainer. | Reuse the same persistent /data volume and Docker socket. |
| Docker Standalone Agent | Stop and remove the Agent, pull portainer/agent:lts, recreate with original mounts and secret. |
The Agent’s Docker host. | Keep Agent and Server versions matched. |
| Docker Swarm | Update Portainer Server and Agent services. | A Swarm manager node. | Back up first and coordinate service image versions. |
Practical pre-flight and post-update checklists
Before the change
- Confirm CE or BE and select the corresponding image.
- Record container or service names, image tag, mounts, ports, flags and secrets.
- Back up Portainer’s persistent data and verify the backup.
- Schedule the change so you can test sign-in and endpoint access immediately.
After the change
- Open the HTTPS endpoint on port 9443 and sign in.
- Confirm the displayed version and that the update notice is gone.
- Check environments, stacks, users and endpoint health.
- Verify Agent connectivity and Edge Agent communication when used.
- Keep the backup and the previous deployment details until the new release has operated normally.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
