The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →The safe way to update Docker on an Ubuntu VPS is to make the change reversible, use Docker’s stable APT repository, upgrade the Engine and its companion packages together, and verify the workload immediately. Take a restorable VPS snapshot first, preserve /etc/docker/daemon.json and deployment files, record the current state, then choose between a planned daemon restart and patch-only live restore.
Antihost offers VPS plans with one-click Docker, NVMe storage and a 14-day free trial.
This runbook covers Ubuntu 22.04, 24.04 and 26.04 installations, including amd64 and arm64 systems. Package names, release support and repository details can change, so check Docker’s current “Install Docker Engine on Ubuntu” documentation for your VPS before running the commands.
As an Amazon Associate I earn from qualifying purchases.
Free tools Windows power users keep installed
One-click scans. No signup required.
What a safe Docker update actually protects
An update changes more than the docker command. A normal Ubuntu installation involves the Docker Engine daemon, its CLI, containerd, Buildx and the Compose plugin. A daemon restart can briefly interrupt containers, while an incompatible configuration can prevent Docker from starting at all. The objective is therefore not merely to install a newer package; it is to preserve a known-good recovery path and prove that the application still works afterward.
A production-safe change has four properties:
- Recoverability: a tested VPS snapshot or backup and copies of the files needed to recreate the service.
- Known state: an inventory of containers, images, volumes, networks, ports and health checks, plus the exact installed versions.
- Controlled source: Docker’s official stable repository, with versions selected deliberately rather than an unrelated package source.
- Immediate validation: daemon, container, port and application checks, followed by a defined rollback if any check fails.
1. Establish a recovery point before changing packages
Confirm two ways into the server
Keep an SSH session open and confirm that you can authenticate again in a second session. If your VPS provider offers a serial, web or emergency console, test that access before starting. A package change that breaks networking, SSH or the Docker service is much easier to recover from when the provider console is known to work.
#1 Best Overall
- [Ultra-Lightweight Ear Buds Designed for Small Ears] Each earbud weighs only 3.7g and features a compact, ergonomic in-ear design made especially for small ears. Secure, low-profile, and comfortable for workouts, all-day wear or overnight sleeping.The ultra-slim profile sits flush in your ear with no hard edges poking or rubbing, so you can even sleep on your side without discomfort.
- [Immersive Stereo Sound with TOZO OrigX Technology] TOZO OrigX tuning delivers clear vocals, balanced mids, and natural stereo sound for music, podcasts, and videos.
- [Long Battery Life for Daily Use] Get up to 7 hours of playtime on a single charge, with up to 32 hours total using the charging case—ideal for workdays, commuting, and extended listening sessions.
- [Bluetooth 5.3 & Stable Connection] Bluetooth 5.3 provides fast pairing, stable wireless performance, and reduced dropouts as you move around home or office.
- [Deep Bass with Clear Vocals] High-performance drivers produce punchy bass while keeping vocals clean and detailed for everyday listening.
Take a restorable snapshot or backup
Create a provider snapshot or another backup that can restore the entire VPS, and check that the provider labels it as completed rather than merely scheduled. Record its timestamp and retention period. A snapshot is the fastest broad rollback, but it does not replace file-level copies: you still want the exact daemon configuration and deployment definitions available if only Docker needs to be restored.
Save configuration and deployment inputs
Copy these items to storage outside the VPS, with a date in the filename and permissions that keep secrets private:
/etc/docker/daemon.json, if it exists.- Docker Compose files, override files and the directory from which each stack is deployed.
- Environment files, secret references, registry credentials and the documented process used to retrieve secrets. Do not paste secret values into a ticket or shell history.
- Systemd overrides, proxy settings, firewall rules and any automation that starts or updates containers.
Back up the files that describe how data is mounted, but do not assume that a Compose file contains the data itself. Persistent application data in Docker volumes or bind-mounted directories needs its own application-consistent backup. Databases should be dumped or backed up using their documented procedure before relying on a filesystem snapshot.
Record the current Docker state
Save command output to a dated text file. This gives you a comparison point and tells a rollback operator exactly what “known good” means.
date -u
sudo docker version
sudo docker info
sudo systemctl status docker --no-pager
sudo systemctl is-active docker
sudo systemctl is-enabled docker
docker ps --all
sudo docker image ls
sudo docker volume ls
sudo docker network ls
docker compose ls
sudo ss -ltnup
sudo df -h
sudo df -iFor each running service, record its container name, image tag or digest, restart policy, mounts, environment-file reference, published ports and health status. The following views are useful when you need a compact inventory:
docker ps --format 'table {{.Names}}t{{.Image}}t{{.Status}}t{{.Ports}}'
docker inspect --format '{{.Name}} {{.Config.Image}} {{.State.Health.Status}}' $(docker ps -q)If a container has no health check, write down the application endpoint or representative request you will use after the upgrade. Capture the current APT package versions as well:
apt list --installed 2>/dev/null | grep -E 'docker|containerd'
apt-cache policy docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-plugin2. Check Ubuntu, architecture and Docker’s release policy
Verify the VPS release and CPU architecture
Docker’s Ubuntu documentation lists Ubuntu 22.04 (Jammy), 24.04 (Noble) and 26.04 (Resolute) as supported releases at the time of this guide. It lists common architectures including amd64 and arm64, as well as armhf, ppc64le and s390x. Confirm your actual platform rather than inferring it from the provider’s product name:
. /etc/os-release && printf '%s %sn' "$ID" "$VERSION_ID"
dpkg --print-architecture
uname -mRead the current Docker Ubuntu installation page immediately before an upgrade. Support matrices and repository metadata can change, particularly around a newly released Ubuntu version. If your release or architecture is not listed, stop and resolve that support question instead of forcing packages from a different distribution.
Rank #2
- 【IP68 Waterproof Multifunctinal Smart Watch】Torjalph fitness activity tracker smart watch is IP68 waterproof technology ,you can wear it when swimming,handwashing,it's rain-proof which means that you perform multiple exercise modes outside without worrying about sweat or rain corroding your fitness smart watch,and this watch equipped with a 230 mAh large capacity battery magnetic charging ,and this sports activity tracker watch can be used 5-7 days If fully charged.
- 【Larger 1.83'' Full Screen Watch & Multi-dial Selection】1.83 inch full HD color touch screen smart watch for men / women provides excellent 240*284 resolution image quality ,This Bluetooth smart watch offers a better touch experience and remarkable immersion and ,more than 200 watch faces for you to choose from App"Da Fit ", you can change the dial style according to your mood to wear keeping the world on your wrist
- 【Accurate Activity Tracker Smart Watch 】sports watch activity tracker uses sweat and dust resistant breathable silicone strap, our Fitness Tracker Smart Watch for Android iOS Phones supports 12 sports modes,walking,running,bicycle,swimming,badminton,basketball,football,rope skipping. This bluetooth calls smart watch for men women is lightweight and stylish, bringing more convenient and relaxing sports experience while also providing more protection.
- 【Your 24 Hour Personal Daily Health Monitor】Fitness watch for women men full touch screen IP67 waterproof bluetooth smartwatch for Android iOS Phones with heart rate blood pressure monitor multifunction Andriod smart watch with steps counter sleep monitor sports fitness watch, monitoring blood oxygen saturation allows you to understand your physical condition in real time to track fitness progress ,to know your health status in time.
- 【More Functions Bluetooth Call Smart Watch】This fitness activity smart watch full screen for iPhone and Android phones includes a bunch of new features including:The bluetooth smart watch can hang up the phone, receive and display WhatsAPP /Text /Facebook /Twitter /Messenger reminder.Support sedentary reminder, alarm clock, stopwatch, timer,weather information,music control, remote camera control compatible with Android 5.0 and above or iOS 9.0 and above smartphones.
Use the stable channel for routine production work
Docker documents stable and test channels. Stable is the appropriate default for a production VPS; the test channel is for evaluating upcoming builds in an environment where a regression is acceptable. Patch releases are described as backward compatible within their major and minor version, but that does not eliminate the need to test your workload.
Decide whether you need the newest stable build or a controlled, pinned version. A pinned version lets you stage the same package set on another VPS and schedule a later rollout. The newest stable build reduces the time you remain on an older security and bug-fix level, but it still requires a rollback plan.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
| Approach | When it fits | Main operational consequence |
|---|---|---|
| Latest stable | Routine maintenance when your staging or canary checks are healthy | Less version drift, but the candidate can change between planning and execution |
| Pinned stable version | Regulated, staged or repeatable rollouts | You must retain the exact package version and ensure it remains available in the repository |
| Patch-only live restore | A Docker daemon patch update where avoiding container shutdown is important | Requires the documented live-restore conditions and still needs post-update checks |
| Planned restart | Major or minor daemon changes, skipped releases or workloads that require certainty | Schedule a maintenance window and allow time for orderly stop/start and validation |
3. Make sure the official repository is configured
Docker’s documented Ubuntu repository flow places the signing key at /etc/apt/keyrings/docker.asc and creates /etc/apt/sources.list.d/docker.sources. An existing installation should use that same official source rather than mixing packages from the Ubuntu archive, an old third-party repository and manually downloaded files.
Inspect the configured source and candidate versions before installing anything:
grep -R --line-number --no-messages 'download.docker.com|docker-ce' /etc/apt/sources.list /etc/apt/sources.list.d
sudo apt update
apt list --all-versions docker-ce
apt-cache policy docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-pluginIf the signing key or source file is missing, follow Docker’s current repository setup instructions rather than copying a command from an outdated blog post. The documented package set is:
docker-ce(Engine)docker-ce-cli(command-line client)containerd.iodocker-buildx-plugindocker-compose-plugin
Do not combine an Engine from one source with a CLI, containerd or plugins from another unless Docker’s documentation explicitly requires it. The package manager should resolve one coherent set from the selected repository.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errorsPin a version when the rollout needs to be repeatable
After apt update, copy the exact candidate string shown by apt list --all-versions docker-ce. Docker’s upgrade instruction is to follow step 2 of its installation instructions and choose the new version. On systems where a specific version is required, install that same version for each package for which the repository exposes a matching candidate:
sudo apt install
docker-ce=<VERSION>
docker-ce-cli=<VERSION>
containerd.io
docker-buildx-plugin
docker-compose-pluginReplace <VERSION> with the repository’s actual version string; do not guess its suffix. If a matching companion package cannot be resolved, stop and investigate the repository metadata rather than forcing an incomplete upgrade. For an ordinary latest-stable update, omit the version pin and review the proposed transaction carefully before accepting it.
Rank #3
- [Low Noise High Fidelity] New bee guitar cord with 22AWG oxygen-free-copper center conductors provides enhanced signal transfer, the PVC insulation material and the high-density stranded copper double shield provide noise rejection for quiet operation
- [Ideal for Choice] New bee 1/4 straight and right angle metal connectors, ensures a secure connection in any instrument, pedal, or amp jack. L shape great fro on stage guitar stands
- [Wide Compatible] Suitable for mixer, power amplifier, microphone, effector, decoder, equalizer, electoronic organ, electric guitar, electric bass and other electronic equipments. Widely used in the installation of smart home, karaoke speaker, professional stage audio, etc
- [Easy Disassemble] Making incidental repairs quick and easy! Very nice, flexible cable
- [Dont Hesite to Order] 24 hours customer services and professional technology team are standing by
4. Review daemon configuration before the package change
On a normal Linux installation, Docker reads /etc/docker/daemon.json. Make a dated copy and validate its JSON before touching packages:
sudo cp -a /etc/docker/daemon.json
/etc/docker/daemon.json.$(date -u +%Y%m%dT%H%M%SZ)
sudo python3 -m json.tool /etc/docker/daemon.json > /dev/nullReview storage-driver, registry, logging, proxy and live-restore settings. Check that referenced directories exist and have the expected ownership and free space. Docker warns that specifying the same option both as a startup flag and in the JSON file prevents the daemon from starting. For example, a systemd unit or drop-in that supplies a flag must not repeat that setting in daemon.json. If the two sources conflict, remove the duplicate or make one source authoritative before upgrading.
Keep the pre-change file alongside the package-version record. A rollback that restores packages but leaves a changed daemon configuration can reproduce the failure instead of fixing it.
5. Decide whether live restore is appropriate
Docker’s live-restore feature can keep Linux containers running while the daemon is unavailable, which can reduce downtime during a planned daemon update. It is a continuity aid, not a guarantee that an upgrade is interruption-free.
Docker documents live restore as supported for patch releases in the YY.MM.x form, not for a major or minor daemon upgrade written as YY.MM. If releases are skipped, the daemon may fail to reconnect to running containers and manual intervention may be required. Treat a patch-only live-restore rollout differently from a major or minor upgrade: the latter belongs in a maintenance window with a tested stop/start and recovery procedure.
If you already use live restore, confirm the setting in daemon.json and include a controlled restart test in your operational planning. Do not enable it for the first time during an urgent upgrade without understanding how your storage, networking and monitoring behave when the daemon is detached from running containers.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →6. Perform the coordinated upgrade
Use a maintenance window when a restart is not acceptable
Notify anyone who depends on the VPS, pause deployments and ensure monitoring alerts are understood. Keep the SSH and console sessions open. For a planned restart, reserve time for package installation, daemon startup, application checks and rollback. Do not begin while an unrelated kernel, firewall or storage change is in progress; isolating variables makes failures diagnosable.
Refresh metadata and install the complete package set
Run the package transaction as one coordinated change:
Rank #4
- Digital Family Calendar: BSIMB digital calendar wall touch screen puts an end to your chaotic life. Designed for busy families, the digital calendar keeps you organised and in step with your family. Assign different colours and tasks to each family member to make family scheduling easier and more intuitive.
- Easy Setup and Auto-Sync: Plug in, connect to WLAN and auto-syn your electric calendar in minutes. Digital wall calendar compatible with Google calendar, iCloud calendar, Outlook calendar, Cozi calendar and Yahoo calendar. Add events directly on the device or through the ecalendar app. Electronic calendar stays current whether you're at work or traveling—no manual updates needed.
- All-In-One Home Assistant: Smart calendar builds habits and encourage independence with personalised chores. Display daily meal plan to reduce the daily ‘What's for dinner?’ stress. To-do lists keep track of everything you want. Turning chores into valuable achievements with stars and rewards, making life easier and more enjoyable.
- Manage Anytime Anywhere: BSIMB electronic calendar for family stay connected with the powerful ecalendar app. Access and manage your digital wall calendar anytime, anywhere with free features like stars & rewards, photo screensaver, chore charts, meals plans, to-do lists etc. Electronic planner paid features like Magic Import tailor advanced tools for users with special needs.
- Stay in Touch with Loved Ones: Share photos or videos from your phone to electronic wall calendar with app, instantly update your life moment, and keep in touch with your family, especially those who are far away; you can also surprise your smart calendar digital wall by sending him a wish card; it's also great for keeping tech-illiterate elders in touch with the youngsters.
sudo apt update
sudo apt install docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-pluginFor a pinned rollout, use the approved version syntax from the previous section and verify the transaction’s removal, upgrade and installation list before answering yes. Avoid Docker’s convenience installation script on a production VPS; Docker describes that script as intended for testing and development environments. The official APT repository gives you package provenance and lets APT show the exact versions it will install.
Do not run an automatic cleanup that removes old images or volumes as part of this maintenance. Unused data can be reclaimed later through a separately reviewed housekeeping task; deleting it during an upgrade makes recovery harder.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.7. Verify the daemon, containers and application immediately
Check service state and versions
Start with the same basic checks you recorded before the change:
sudo systemctl status docker --no-pager
sudo systemctl is-active docker
docker version
docker infoDocker’s installation guide uses systemctl status docker and docker run hello-world as basic installation checks. Run the image test only if pulling an image is acceptable for your environment and your registry policy permits it:
sudo docker run --rm hello-worldConfirm that the client and server versions are the expected pair, the storage driver is unchanged unless you deliberately changed it, and the configured registries, logging driver and live-restore setting are present.
Recommended Free Tools
Compare the workload with the pre-change inventory
docker ps --all
docker compose ls
docker volume ls
docker network ls
docker ps --format 'table {{.Names}}t{{.Image}}t{{.Status}}t{{.Ports}}'Check every expected container, not just the first one listed. Verify restart policies, mounts, health status and published ports:
docker inspect --format '{{.Name}} restart={{.HostConfig.RestartPolicy.Name}} health={{.State.Health.Status}}' $(docker ps -q)
sudo ss -ltnupA container shown as “Up” can still serve an unusable application. Inspect unhealthy containers, recent restarts, missing mounts and changed image IDs before declaring success.
Read the Docker journal
sudo journalctl -u docker --since '-15 min' --no-pagerLook for configuration parse errors, storage-driver failures, permission problems, failed registry connections, network-controller errors and repeated container restarts. Save the relevant log output with the package versions; it is essential if you need support or a rollback.
Exercise a real application path
Call the application’s health endpoint or make a representative request from the same network path used by customers. Check TLS termination, reverse-proxy routing, background workers, scheduled jobs and one read/write operation where it is safe to do so. Confirm that metrics and log collection still receive data. A successful daemon check proves only that Docker started; the application request proves that the workload survived.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstall8. Roll back decisively when validation fails
Stop the rollout at the first failed health, port, data or application check. Do not repeatedly restart a broken daemon while changing several variables; preserve evidence first.
- Record the new Docker, containerd, Buildx and Compose versions, the exact error messages and the time of failure.
- Save
sudo journalctl -u docker --since '-30 min', package-manager output and the currentdaemon.json. - Prevent an automated deployment from recreating containers while you investigate.
- Restore the prior known-good package versions from the repository if they are still available, and restore the dated
/etc/docker/daemon.jsoncopy. - If package rollback is uncertain or the host is broadly inconsistent, revert the VPS snapshot or backup according to the provider’s documented procedure.
- Run the full verification checklist again: service status, versions, container inventory, health checks, ports, journal and an application request.
APT can show versions still available in the repository:
apt list --all-versions docker-ce
apt-cache policy docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-pluginUse the exact prior version recorded before the upgrade, not merely the word “oldest.” If that version is no longer available, the snapshot is usually the more reliable restoration path. After recovery, document the package versions, error, restored configuration and result before attempting another rollout.
9. Troubleshoot the failure modes that matter most
Docker will not start after the update
- Check
sudo systemctl status dockerandsudo journalctl -u docker -b --no-pager. - Validate
/etc/docker/daemon.jsonas JSON. - Look for an option duplicated between the systemd startup flags and the JSON file; Docker states that this conflict prevents startup and produces an error.
- Check storage-driver paths, registry certificates, proxy values and permissions.
- Restore the dated configuration and known-good packages if the cause is not immediately clear.
The daemon starts but containers are missing
- Compare
docker ps --allwith the saved inventory. - Confirm that Docker is using the expected data root and storage driver.
- Check whether the containers were managed by Compose, another systemd unit or an external orchestrator and use that original start procedure.
- Do not recreate containers until you have verified that their original volumes and networks still exist.
Containers run but the application is unreachable
- Compare published ports with the pre-change record and inspect host listeners with
ss. - Check container health output, reverse-proxy configuration and firewall rules.
- Review the Docker journal for network-controller or bridge errors.
- Test locally on the VPS and then through the normal external path to distinguish an application failure from a firewall or load-balancer problem.
Live restore did not reconnect cleanly
Confirm that the change was a patch release and that releases were not skipped. For a major or minor upgrade, or when the daemon cannot reconnect, follow the planned manual intervention path: preserve logs, stop affected containers if necessary, restore the known-good package/configuration pair or snapshot, and validate every service before reopening traffic.
10. A reusable preflight and postflight checklist
Before the upgrade
- SSH and provider-console access tested.
- Restorable VPS snapshot or backup completed and timestamped.
daemon.json, Compose definitions, environment files and secret-handling references copied securely.- Application data backups completed where required.
- Ubuntu release and architecture checked against Docker’s current support page.
- Stable repository and candidate package versions reviewed.
- Container, image, volume, network, port and health inventory saved.
- Live-restore suitability and maintenance-window decision documented.
After the upgrade
- Docker service is active and enabled as intended.
- Engine, CLI, containerd, Buildx and Compose versions match the approved change.
- Expected containers, volumes, networks, mounts and ports are present.
- Health checks pass and no unexpected restart loop appears.
- Docker journal contains no unresolved startup or storage errors.
- Health endpoint and representative application request succeed.
- Monitoring, logs, scheduled jobs and backups still operate.
- Package versions, validation results and any anomalies are recorded.
How often should you update Docker?
There is no universal interval that is safe for every VPS. Track Docker’s stable releases and your Ubuntu security-maintenance schedule, then batch routine updates into a window that your workload can tolerate. Test the selected package set on a staging or canary host when possible. Apply urgent security fixes sooner, but keep the same snapshot, configuration backup, coordinated-package and verification discipline.
The practical rule is simple: never make an unrecorded, irreversible Docker change on the only copy of a production workload. A short preparation phase is what turns a daemon restart into routine maintenance rather than an emergency recovery.
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.
