Recommended Free Tools
Short answer: pull the desired repository tag in Portainer, then recreate the container with Duplicate/Edit while retaining its environment variables, ports, networks, restart policy, and volume or bind mounts. Pulling an image by itself does not change a container that is already running.
Antihost offers VPS plans with one-click Docker, NVMe storage and a 14-day free trial.
For a Portainer stack, use the stack’s update controls instead of editing the generated container. Turn on Re-pull image, and use Force redeployment only when you deliberately want every service recreated. The safe workflow is the same in both cases: identify what owns the deployment, protect persistent data, record a rollback reference, update, and verify the application.
As an Amazon Associate I earn from qualifying purchases.
What “latest image” means in Portainer
Docker images are downloaded snapshots identified by a repository and tag, such as example/app:latest or example/app:2.4. The tag is a pointer maintained by the registry. When an image publisher moves that pointer, the same tag can refer to a different image digest. Portainer can pull the image currently published under the tag you specify, but it cannot make an old tag become a newer release.
That distinction matters when someone says “update to the latest.” Usually they mean “pull the newest image behind the tag this container already uses.” If you instead want a new release line, enter that release tag explicitly after checking the image publisher’s compatibility notes. A moving tag is convenient for routine updates; a digest or fixed version tag is more reproducible and easier to roll back.
#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.
Check ownership and prerequisites first
Do not start by clicking a generated container if it belongs to a stack. First establish how it was deployed and whether the host has enough access to complete the pull.
Identify a standalone container or a stack service
- A container created directly from Portainer’s container screen is normally updated with Duplicate/Edit.
- A container created by a Compose-style Portainer stack is controlled by the stack definition. Editing the generated container can be temporary because the next stack deployment may overwrite it.
- If several containers share a stack, update the stack so its service definitions remain the source of truth.
Confirm registry access
The Portainer environment must be able to reach the registry, authenticate when required, and pull the architecture supported by the host. Check credentials before scheduling a replacement for a critical service. A successful status check is not proof that the image download will complete; the actual pull can still fail because of authentication, rate limits, DNS, TLS, storage, or an unsupported platform.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Record the current version and configuration
Before changing anything important, note the current image repository, tag, and preferably its digest. In the container’s edit screen, record environment variables, published and exposed ports, networks, restart policy, command or entrypoint overrides, health-check settings, and every volume or bind mount. This record is your rollback reference and helps detect an accidental omission during recreation.
Decide what data must survive
Containers are replaceable runtime instances; data written only into their writable container layer is not a safe backup. Databases, uploaded files, certificates, and application configuration that must survive a replacement should live in Docker volumes or bind-mounted host directories. Confirm that those mounts point to the intended locations before deploying the replacement.
Read Portainer’s image status indicator
Open Containers and inspect the image status shown for the container. Portainer uses three indicators:
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
- Green tick: the local image is current according to the status check.
- Orange cross: Portainer found a newer image in the remote registry for the repository and tag being used.
- Grey hyphen: Portainer cannot determine the status, so you must not treat it as proof that the image is current.
Use the reload control to run the check again if the indicator is grey, if registry credentials were recently changed, or if the publisher has just announced an update. The indicator compares the local image with the remote tag; it does not evaluate whether the application release is compatible with your data or configuration.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Update a standalone container step by step
The standalone workflow has two separate operations: download the image, then create a replacement container from the new image. Keeping those operations distinct makes failures easier to diagnose.
1. Pull the image from the Images page
- In the Portainer environment, open Images.
- Choose the registry that hosts the image. Use the registry account required for a private repository.
- Enter the repository name and the exact tag you intend to run. To follow the existing moving tag, use the same repository and tag currently shown in the container configuration.
- If the environment has multiple nodes, select the node on which the container will run. The image is local to a node; pulling it on one node does not place it on every node.
- Click Pull the image and wait for the operation to finish. Review the result for authentication, disk-space, network, or platform errors.
At this point the newer image is available locally, but the running container still uses the old image. Do not stop at the successful pull message.
2. Open Duplicate/Edit
- Return to Containers and open the target container.
- Choose Duplicate/Edit. Portainer presents the settings it will use to create a new container.
- Compare the edit screen with the configuration record you made before the update. Preserve every setting that the application needs, not only the image name.
3. Preserve runtime settings
At minimum, verify the environment variables, published ports, attached networks, restart policy, command and entrypoint overrides, health-check options, and volume or bind mounts. Also check labels, privileged or capability settings, device mappings, resource limits, user and group settings, and logging options when the service depends on them. An image update can appear to fail when the real problem is a missing setting that was not copied into the replacement.
4. Deploy the replacement
- Click Deploy the container.
- When Portainer asks whether to replace the existing container, confirm Replace.
- Wait for the old instance to be removed and the new instance to start. The replacement receives a new container identity even though it uses the same application configuration.
Portainer describes this behavior as creating a new container with the updated settings and replacing the old one. Any external script that refers to the old container ID must therefore be updated to use a stable name, label, service discovery method, or other deliberate reference.
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)
5. Verify the result
- Confirm that the replacement container shows a running state.
- Open its logs and look for startup errors, failed migrations, permission problems, missing files, or repeated restart messages.
- Test the application through its normal health endpoint, web interface, login page, client connection, or other service-specific check.
- Exercise a data path that matters, such as reading an existing record or opening an existing upload. A container can be running while the application is unable to reach its database or mount.
Settings that must survive a replacement
The following checklist catches the omissions that most often turn a routine image refresh into an outage.
| Setting | Why it matters | What to check in Duplicate/Edit |
|---|---|---|
| Environment variables | They commonly contain database hosts, credentials, feature flags, time zones, and paths. | Compare names and values with the previous container; check multiline values and secrets for truncation. |
| Published ports | Clients connect to host ports, not merely to an internal container port. | Confirm host-to-container mappings and the intended protocol. |
| Networks | Network membership controls service discovery and access to databases, proxies, and queues. | Keep every required network and verify aliases if other services use them. |
| Volumes and bind mounts | These hold data outside the replaceable container layer. | Check source paths, destination paths, read-only flags, and the selected volume name. |
| Restart policy | It determines whether the service returns after a reboot or failure. | Retain the previous policy unless the update intentionally changes recovery behavior. |
| Command and entrypoint | An override can select a worker mode, configuration file, or migration command. | Ensure the replacement starts the same intended process. |
| Permissions and devices | UID/GID, capabilities, GPU or USB devices, and privileged mode can be required by the application. | Compare security and device options before deployment. |
Use “Always pull the image” when a cached image is a risk
Portainer can be instructed to pull from the registry rather than reuse a cached local copy. In the container deployment or recreation settings, enable Always pull the image. This is useful when a mutable tag may have moved since the last pull, when several operators use the same host, or when you want the deployment action itself to refresh the image.
Always pull does not replace the configuration review. It only controls image retrieval. You still need to preserve mounts and runtime settings, and you still need to recreate the container for the running process to use the newly pulled image. If the registry is unavailable, an always-pull deployment can fail even when a usable image is already cached locally; plan that trade-off for disconnected or maintenance-sensitive environments.
Protect data and prepare a rollback
Why mounts are the safety boundary
A replacement starts with a fresh writable layer. Anything stored only there belongs to the old container and should be considered disposable. Docker volumes and bind mounts keep data outside that layer, so the replacement can attach the same storage. This does not remove the need for backups: a bad migration, an application bug, or an operator error can damage a mounted database just as it can damage any other live data.
What to record before deployment
- The current repository and tag.
- The current image digest, when available.
- The exact volume names and host paths.
- The environment variables and application configuration files.
- The time of the last known-good verification.
Tags can move, so a previous tag is not always an immutable rollback target. A digest identifies the exact image content that was running. Keep the old image available until the replacement passes its checks, subject to your host’s storage limits.
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
Rollback procedure
- Stop or otherwise take the failing replacement out of service so it cannot continue writing inconsistent data.
- Use the recorded previous tag or digest in the image field. If the old local image was removed, pull that exact reference again.
- Choose Duplicate/Edit on the failed replacement or recreate from the original definition, restoring the same environment variables, ports, networks, restart policy, and mounts.
- Deploy and confirm Replace.
- Inspect logs and perform the same application-level verification used after the update.
Rolling back the image does not automatically undo a database schema migration performed by the newer release. Consult the image publisher’s release notes for migration and downgrade rules before attempting a rollback of a stateful application.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Update a Portainer stack correctly
Stack-managed services should be changed through the stack, because the stack definition is the authoritative description of the deployment.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
1. Open the stack and review its definition
Confirm the service image repository and tag in the Compose-style definition. Review named volumes, bind mounts, environment entries, networks, ports, dependencies, and any secrets or configuration references. If the definition is sourced from Git or another external location, make the change there when the source is authoritative rather than relying on a local edit.
2. Enable Re-pull image
When updating the stack, enable Re-pull image to retrieve the current remote image for the configured tag. Portainer documents this as equivalent to Docker’s --pull=always. It prevents the update from silently reusing an older local copy.
3. Decide whether Force redeployment is necessary
Enable Force redeployment when you need the stack’s containers recreated even though the stack definition itself has not changed. This can be useful after a tag moved in the registry or when a service must be recreated to pick up an image already pulled. It can also overwrite local changes, so use it only when the stack source is correct and treated as authoritative.
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.
4. Deploy and verify every affected service
- Apply the stack update with the desired pull and redeployment options.
- Watch the service and container states until replacements report as running.
- Inspect logs for each service, not only the front-end service.
- Check inter-service connectivity, persistent volumes, migrations, and the application’s normal health or login path.
Do not edit one generated container as a shortcut. The next stack update can restore the definition’s previous image or settings, making the apparent fix disappear.
Automate updates with Portainer webhooks
Portainer Business Edition supports webhooks for containers and stacks. A webhook can trigger a redeployment that pulls the current image behind the same tag, or it can update a service to a different tag according to the webhook configuration.
For a stack webhook, the request can include pullimage=false when the pull must be prevented. That option is useful when images are preloaded through a controlled pipeline or when registry access is intentionally unavailable during deployment. Webhooks are optional automation, not a substitute for persistent storage, compatibility checks, or post-deployment health verification.
Container webhooks are unavailable in Edge Agent-only environments according to Portainer’s container webhook documentation. Verify that your environment and Portainer edition support the feature before designing an automated update process.
Troubleshoot common update failures
| Symptom | Likely cause | Action |
|---|---|---|
| The image status is a grey hyphen. | Portainer could not compare the local image with the registry. | Reload the status, verify registry credentials and network access, then perform an explicit pull from Images. |
| Pull fails with an authentication error. | The repository is private or the selected registry account lacks access. | Choose the correct registry and credentials, then retry. Confirm the repository and tag spelling. |
| Pull succeeds but the old version is still running. | Only the image was downloaded; the existing container was not recreated. | Use Duplicate/Edit, deploy the replacement, and confirm Replace. |
| The replacement exits immediately. | The new image may require a changed command, environment variable, permission, architecture, or configuration format. | Read the container logs, compare the edit screen with the previous configuration, and check the image publisher’s release notes. |
| The container runs but the application has no data. | A volume or bind mount was omitted, changed, or attached to the wrong path. | Stop the replacement, correct the mount source and destination, and recreate it with the original storage. |
| Clients cannot connect after the update. | A published port, network, alias, proxy setting, or firewall-related option changed. | Compare port mappings and network membership with the recorded configuration, then test from the client side. |
| The stack update restores an old setting. | The generated container was edited instead of the stack definition. | Change the authoritative stack source and redeploy with the appropriate pull option. |
| The stack keeps recreating services. | Force redeployment is enabled or the definition is changing on every update. | Disable force redeployment unless it is intentional, and check the source definition for unstable values. |
| Automatic webhook updates do not run. | The environment may be Edge Agent-only or the webhook lacks permission or registry access. | Confirm Business Edition support, webhook configuration, endpoint reachability, and image-pull credentials. |
Choose the right update method
| Decision factor | Standalone container | Portainer stack |
|---|---|---|
| Deployment owner | The individual container configuration. | The stack definition and its source. |
| Normal update control | Pull the image, then Duplicate/Edit and replace. | Update the stack with Re-pull image; use force redeployment only deliberately. |
| Configuration persistence | Preserve settings in the replacement form or recreate from documented configuration. | Change the stack definition so future deployments retain the update. |
| Reproducibility | A moving tag is convenient; a version tag or digest is more deterministic. | The same tag and pull policy apply to every service replica or recreation. |
| Persistent data | Use Docker volumes or bind mounts, never the container layer for required data. | Declare and preserve volumes or bind mounts in the stack definition. |
| Automation | Manual deployment or a supported container webhook. | Stack update workflows or a stack webhook, with optional pull suppression. |
Final verification checklist
- The intended repository and tag, or an exact digest, were selected.
- The image pull completed on the node that will run the service.
- The replacement or stack service is running.
- Environment variables, ports, networks, restart policy, commands, permissions, and devices match the intended configuration.
- Every required volume or bind mount is present at the correct destination.
- Logs show a clean startup and no repeated crash loop.
- The application’s own health, login, client connection, and representative data checks succeed.
- The previous tag or digest and configuration record are retained until the update is accepted.
The reliable Portainer pattern is therefore simple but deliberately two-stage: obtain the image you intend to run, then recreate the correct deployment around it. Treat standalone containers and stack services according to their ownership model, keep state outside replaceable containers, and make the image reference precise whenever rollback or reproducibility matters.
Quick Recap
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.
