About this article: This article is reviewed against the cited sources. This is source research, not lab validation. Check the stated versions and your own requirements before making changes.
A container suits an application that was built or repackaged to run as a container image, keeps its important data outside the container, and has someone who will maintain the images. A full virtual machine suits an application that is installed with a setup program, configured through a desktop console, or supported by the vendor only on a named server operating system. If yours matches that description, start from a virtual machine. The deciding question is not which technology is newer; it is what your vendor supports and who will run it.
Why it matters
Containers are often described as lighter and faster to deploy, and for software designed for them that is true. But moving a traditional business application into a container without vendor support can leave you with an unsupported system, data that disappears when the container is replaced and a new skill set to hire. Knowing the difference lets you ask your vendor the right question before spending on a migration.
How it works
What a virtual machine is
A virtual machine behaves like a complete server. Docker's own documentation describes a virtual machine as "an entire operating system with its own kernel, hardware drivers, programs, and applications". You install and manage the application inside it the same way you would on a physical server.
What a container is
Docker describes a container as "an isolated process with all of the files it needs to run", and notes that multiple containers "all share the same kernel", which is why more applications fit on less infrastructure.
Two consequences matter for business applications.
Data inside a container is temporary unless you plan otherwise. Docker's storage documentation explains that files created inside a container are stored on a "writable container layer" and that "data written to the container layer doesn't persist when the container is destroyed". Its storage-driver page is explicit about the boundary: "When the container is deleted, the writable layer is also deleted. The underlying image remains unchanged." Deleting and recreating a container is routine, for example to apply an updated image, so anything kept only in that layer goes with it. Data that must last belongs in a volume or other storage mounted from outside: Docker's guide on persisting data says "Volumes are a storage mechanism that provide the ability to persist data beyond the lifecycle of an individual container." Databases, uploaded documents and configuration belong there.
Windows containers are tied to the host's Windows version. Microsoft's compatibility guidance says that where host and container versions do not match, compatibility is "possible, but not guaranteed, and thus the container image will be prevented from running on the host". The match that matters is the Windows build number: Microsoft notes that "the build number only changes when new versions of the OS are published, and the revision number is updated as Windows updates are applied", and from Windows Server 2019 onwards host and image revisions need not match. Monthly updates are therefore rarely the deciding factor for process isolation, though they still matter for security and for what the vendor supports; a host upgrade to a new Windows Server release is the bigger planning event. The rule is not a simple "same build only" either: Microsoft's compatibility tables list combinations that are supported anyway, such as a Windows Server 2022 image with process isolation on a Windows Server 2025 host. Running with Hyper-V isolation gives the container "a set of matching Kernel binaries" inside "an optimized VM", but it does not make every combination work: the same tables show, for example, that a Windows Server 2019 host cannot run a Windows Server 2022 image in either mode. Check the exact host and image pair against Microsoft's tables before planning a host upgrade.
What to choose and why
Signs a container fits
- The vendor publishes a supported container image, or your developers build the application as one.
- The application is a web service or background worker whose data lives in a database or file share outside the container.
- You have, or will pay for, someone to rebuild images when security updates arrive and to run the platform that schedules them.
- You need to run several copies and add more at busy times.
Signs a virtual machine fits
- The application installs with a setup program and stores settings on the local disk or registry.
- Staff or the vendor sign in to the server to run a management console.
- The vendor's support statement names a Windows Server or Linux version, not a container image.
- You want patching and backup to work the way they do for your other servers.
Mixed is normal
You do not have to pick one for everything. A database server and a line-of-business application can stay on virtual machines while a customer-facing web portal runs in containers. Docker notes that "you will see containers and VMs used together": in a cloud environment the provisioned machines are typically virtual machines, each running a container runtime that hosts several applications.
A hypothetical example
A wholesale distributor runs an inventory application installed from a setup program on Windows Server, plus a small web ordering portal written by a contractor. The inventory application's vendor supports only a named Windows Server version; it stays on a virtual machine. The ordering portal is a web service with its data in a separate database; the contractor packages it as a container so new versions can be released without touching the server. The example is illustrative.
Questions to ask your vendor or developer
- Is there a supported container image for this application, and on which host operating system versions?
- Where does the application keep data, settings and uploaded files?
- Who rebuilds the image when a security update is released, and how quickly?
- What runs and monitors the containers, and who looks after that platform?
- How is the data backed up and restored?
Read next
Related articles you may want next.
- HostingManaged, co-managed or self-managed hosting: choosing how much of the server you runHow a business decides which layers of a hosted server it hands to a provider and which it keeps, using staff time, the need for administrator access and the evidence it must produce.Read article
- HostingServer Core or Desktop Experience for hosted business applicationsHow to choose between the Server Core and Desktop Experience installation of Windows Server for a hosted business application: what each includes, why Microsoft recommends Server Core, which roles it cannot run, and why the choice cannot be changed later.Read article
- Backup & RecoveryKubernetes Persistent Data: CSI Snapshots, Velero and Application ConsistencyWhat a CSI snapshot does and does not guarantee, how Velero's three volume methods differ, how far hooks go, and how to prove a restore works.Read article
Risks and limits
- Unsupported repackaging. Placing a traditional application in a container without the vendor's agreement can void support.
- Lost data. Anything written inside a container and not to mounted storage is lost when the container is replaced.
- Patching moves. In our view, container security depends on rebuilding images, not on monthly updates applied inside a running server.
- Windows version coupling. Host upgrades and container images must be planned together, as Microsoft's compatibility tables show.
- Platform overhead. In our view, running containers in production adds an orchestration platform and the skills to operate it.
Sources
Opened 15 November 2026.
- Docker Docs: What is a container?.
- Docker Docs: Storage (opened 16 November 2026, for the writable container layer).
- Docker Docs: Storage drivers (opened 16 November 2026, for deletion of the writable layer).
- Docker Docs: Persisting container data (opened 16 November 2026, for volumes).
- Microsoft Learn: Windows container version compatibility, page shows last updated 23 January 2025 (reopened 16 November 2026 for the build, revision and Hyper-V isolation sentences).
Related article: Kubernetes persistent data: CSI snapshots, Velero and application consistency covers backup once containers hold business data.
Related service: Cloud hosting.
Learning notes
- A virtual machine is a whole server; a container is an isolated process sharing the host's kernel.
- Data kept only in a container's writable layer is deleted with the container; keep databases, documents and configuration on a volume or other mounted storage.
- Windows container images must be a supported pair with the host's Windows build in Microsoft's compatibility tables; Hyper-V isolation widens the choice but does not make every pair work.
- Vendor support, not fashion, should decide the packaging.
- Containers move patching to image rebuilds and add a platform to run.
This article was originally published on .