Cloud servers from $4/mo - Grab the Deal! Let’s start ->
What is a VPS? 4 Tips on How to Choose the Best VPS
Infrastructure
18.10.2021
10 min read
Share
What is VPS? Why do developers around the world use it? Why should you use it? How to choose the best one?
In this article, we will answer all the questions diving deep into every topic.
What does VPS stand for?
This abbreviation could be deciphered as "Virtual private server". Or "Virtual dedicated server" in some cases.
The term itself brings the description of the technology it relates to, actually. Here we are talking about a server — a platform where webmasters and developers store their project’s data or test different ideas (it includes website’s documents, applications’ media, etc.). But this server is not real. It is a virtualized copy of it that works as a fully-fledged PC but uses hardware of another device as its own. VPS can be used to create many such computers that can be simulated using only one physical machine.
Why is it "virtual" and "private"?
It is "virtual" because it exists in the hypervisor — a special application that is installed on a PC and can be used as a full-featured emulator of "real" computers. This emulator takes part of tangible hardware and shares it with an artificial PC using complex virtualization technologies. After that procedure is established the server "looks" like a familiar workspace for developers and webmasters renting it.
It is private because in most cases this kind of server is given full control to the administrator renting it. The whole dedicated infrastructure is controlled by one team and they don’t have to share any resources or data with other users that pay for service of the same hosting.
What is the difference between VPS and VDS?
Let’s talk about virtual dedicated servers a bit more. Sometimes, both abbreviations are used together. Like VDS/VPS. Because they mean the same thing as a product. VPS and VDS are virtual servers that are given full control to one administrator or his team.
But the difference exists and it lies in the technological implementation of virtual servers. VPS is associated with OpenVZ virtualization technology and VDS — with KVM.
But it is important to understand that this designation is very arbitrary. A lot of developers and webmasters use both terms interchangeably.
What is VPS and how does it work?
In general, VPS is a virtual machine that is installed on some PC that can be remotely controlled via a special application or command-line utility.
VPS is a quite cheap way to get your own server without confusing and disturbing functional limitations like in the case of virtual hosting. It costs less because the provider has to buy one physical machine and implement many virtual servers on it instead of buying a PC for every potential webmaster or developer.
And at the same time, VPS is not really limited in its capabilities. It is almost the same in terms of functionality as its counterpart — a dedicated server.
What are VPS's used for?
So, what exactly you can do with VPS and why they’re so necessary for developers and system administrators:
-
It is used to create informational web platforms, online stores, and various kinds of commercial web applications.
-
To store any personal data without go-between services like Dropbox or Google Drive.
-
To develop and test fully functional lightweight applications or MVPs.
-
To deploy chunky and complex software platforms like Odoo, 1C Bitrix, etc.
-
To create personal gaming servers (to make money on it) or mail servers (to anonymize correspondence).
-
To launch and maintain CCTV systems to store a large number of recordings.
There are other use cases for VPS’ but these listed above are the most relevant.
Advantages and disadvantages of VPS
Speaking of benefits, we must pinpoint things like cheapness, independence, less responsibility, good technical equipment. VPS usually costs less than physical servers and at the same time gives capabilities on par with real computers. In most cases, VPS represents an isolated software platform that is accessible by you and your team members. Even the host can’t get inside it and somehow interact with your virtual PC.
Unfortunately, there are a few drawbacks. The performance of VPS will never be as high as the performance of a real computer. Hypervisor and virtualization technologies will be a bottleneck that blocks it from achieving all the potential of used hardware. Further, it is not possible to have any impact on the physical state of the rented PC. Hardware installed in it is installed by the host. You’d never be allowed to change something inside the machine.
Two types of VPS
As we mentioned earlier, there are two virtualization technologies used to create VPS/VDS servers. OpenVZ and KVM. What kind of VPS should you choose? Let’s break them down:
OpenVZ
-
The amount of resources available for your personal service is dynamically changing. If your web project is in heavy usage, the amount of available resources will grow respectively.
-
It is possible to change any characteristics of your PC at any moment without reloading the operating system. Just pay a bit more if you want a more powerful artificial computer.
-
It is possible to lose some amount of performance because other users are accessing the host with you in parallel. So, you’re not independent. Moreover, your data is visible to the host.
-
You can install only Linux OSes to the OpenVZ server because it is based on the Linux kernel.
KVM
-
The volume of hardware resources is static. It is closer to a real PC than in the case with OpenVZ.
-
You can change CPU and RAM but it is necessary to relaunch a server so changes take their place.
-
You’re fully independent. Nobody can access your data, not even host administrators.
-
You can decide by yourself what operating system to install. Even if you choose Windows or macOS.
As you can see, VPS is a much more flexible variant but KVM is more reliable and works as a real PC.
VPS hostings in a nutshell
A hosting provider (also called "host") is a business that creates VPSes and sells access to them to developers and webmasters. The host creates data centers around the world and deploys different applications and websites on them.
Their main task is to make deploying as easy as possible for every user.
VPS in USA: hostings, prices
There are many hosting providers in the USA that are great at doing their job.
-
Bluehost — probably the cheapest VPS and quite a popular platform that gives its users unmetered bandwidth. It also gives users an opportunity to easily migrate from old host to new. Renting a server at Bluehost you are getting a free domain and professional technical support 24/7. It costs about $3/month for the most basic plan.
-
Hostman — modernity is at the core of this service. It is not only amazingly reliable servers based on platforms like AWS, Azure, and Google Cloud. It is also the simplest interface to deploy any application, website, or database in a few clicks. And it is just from $5/month for a powerful platform for your projects.
-
Hostgator — the great multipurpose server that only costs around $4 per month. It gives unmetered disk space and bandwidth, a 45-days guarantee, and a large search credit.
-
DigitalOcean — a basic server at DO will cost you around $5 a month. What’s great about DO — its reliability. It is one of the most fast-growing hostings out there. Functional and modern.
-
AWS — one of the biggest platforms to deploy apps and websites. It is the platform created by Amazon and used by giants like Apple. One of the most functional and reliable. The price depends on the number of projects and their resource capacities.
Is there free VPS out there?
There are but they’re problematic. If your host offers you a free server it comes with many caveats for sure. Like:
-
Obligation to place an ad on your website.
-
Limit of resources.
-
No privacy. Nobody will bother about confidential data.
-
No security. Nobody will defend you from hackers and viruses.
-
Limited functionality.
We don’t recommend using free hosting because there’s no such thing as a free lunch. If you don’t pay for the product — you are the product. Your personal information, your files, your users.
How to choose VPS that fits your needs?
The decision strongly depends on what exactly you need to do with your VPS and what is your working environment. So you must answer some questions before renting the virtual server.
Choose an operating system
It is necessary to select an operating system, whether it will be Windows or some Linux distributive.
Linux is more flexible and lightweight. It is a great choice for small projects and backend systems like databases that are manipulated via command line without any needing for the graphical user interface. Furthermore, Linux is more resistant to hackers’ attacks and resource-intensive tasks.
Windows is an option for users that need to work with Microsoft’s services and products. For example, if your team relies on Teams (tautology intended), Office 365, and Outlook, you’d better consider VPS with Windows onboard. Moreover, it is a nice choice for those of you who want to deploy a remote operating system with a full-fledged graphical interface.
Rent appropriate "hardware"
It is a must to rent a server that is fully capable to deal with the job you’re going to delegate to it. Also, it is really important to pay for a bit more so your project won’t stop working because of exponential user base growth.
The one thing you should definitely consider before renting a server — finding one with SSD storage. It will guarantee delivering the data to users in a most efficient and quick way.
Choose the most effective datacenter
The performance of your websites and applications depends not only on used hardware but also on bandwidth. It is really important to choose a host that can ensure a fast and stable internet connection. Besides that, it would be great to see many data centers around the world so you can deploy your projects as close to your potential users as possible.
Moreover, the host must provide you with security measures like a screening system that blocks malware, security staff which is responsible for protecting servers from any physical impact or thefts. And also it should protect your applications and websites from DDoS attacks and any potential data loss.
Choose VPS that is suitable for the job you’re going to with it
Sometimes you have to choose a host based on more specific criteria. For example, you might need a server that is purposefully created to work with gaming servers. It has specific attributes like accents on more broad bandwidth and capability of fast deploying of gaming worlds. There is a good example of such a server called HostHavoc. It has a highly specialized interface and control panel that allows everyone to create their gaming world in a few clicks.
Some hosts provide amazing server capabilities for trading. Like VPS for Forex that gives you access to an instant executional platform to work with. Additionally, they usually can boast of a professional technical support team that has expertise in trading. So if you’re trying to find the best VPS host for Forex, you should find one with such a technical support team.
Also, we would recommend trying out multipurpose platforms like Hostman. It just asks you what you want to deploy and takes care of the rest. Using Hostman deploying applications, websites, databases, and other stuff is a breeze.
A few tips for those who are going to rent their first VPS
-
Don’t pick a plan with the biggest amount of storage at first. There’s a huge chance for you to overpay. You’d better calculate what SSD you need to launch your project and maintain it.
-
Better to overpay for security measures. If you don’t know how to defend yourself from DDoS attacks, pay someone who’d do this.
-
Don’t rent first found VPS over a long period. The best idea would be to use a testing period. Many hosts give one. For example, Hostman lets new users try out every function of the service for 7 days for free.
Summary
That’s it. VPS is an outstandingly useful tool. The only thing you need to do to make it even more effective is to choose the right one. Consider your priorities and needs while you are going through different hosts and VPSes. Don’t pay forward too much and prioritize not only your needs but users’ of yours. Try VPS by Hostman for 7 days for free to understand if it fits you.
Infrastructure
18.10.2021
10 min read
Share
Similar
Infrastructure
Virtualization vs Containerization: What They Are and When to Use Each
This article explores two popular technologies for abstracting physical hardware: virtualization and containerization. We will provide a general overview of each and also discuss the differences between virtualization and containerization.
What Is Virtualization
The core component of this technology is the virtual machine (VM). A VM is an isolated software environment that emulates the hardware of a specific platform. In other words, a VM is an abstraction that allows a single physical server to be transformed into multiple virtual ones.
Creating a VM makes sense when you need to manage all operating system kernel settings. This avoids kernel conflicts with hardware, supports more features than a specific OS build might provide, and allows you to optimize and install systems with a modified kernel.
What Is Containerization
Containers work differently: to install and run a container platform, a pre-installed operating system kernel is required (this can also be on a virtual OS). The OS allocates system resources for the containers that provide a fully configured environment for deploying applications.
Like virtual machines, containers can be easily moved between servers and provide a certain level of isolation. However, to deploy them successfully, it’s sufficient for the base kernel (e.g., Linux, Windows, or macOS) to match — the specific OS version doesn’t matter. Thus, containers serve as a bridge between the system kernel layer and the application layer.
What Is the Difference Between Containerization and Virtualization
Some, especially IT beginners, often frame it as "virtualization vs containerization." But these technologies shouldn't be pitted against each other — they actually complement one another. Let’s examine how they differ and where they overlap by looking at how both technologies perform specific functions.
Isolation and Security
Virtualization makes it possible to fully isolate a VM from the rest of the server, including other VMs. Therefore, VMs are useful when you need to separate your applications from others located on the same servers or within the same cluster. VMs also increase the level of network security.
Containerization provides a certain level of isolation, too, but containers are not as robust when it comes to boundary security compared to VMs. However, solutions exist that allow individual containers to be isolated within VMs — one such solution is Hyper-V.
Working with the Operating System
A VM is essentially a full-fledged OS with its own kernel, which is convenient but imposes high demands on hardware resources (RAM, storage, CPU).
Containerization uses only a small fraction of system resources, especially with adapted containers. When forming images in a hypervisor, the minimal necessary software environment is created to ensure the container runs on an OS with a particular kernel. Thus, containerization is much more resource-efficient.
OS Updates
With virtualization, you have to download and install OS updates on each VM. To install a new OS version, you need to update the VM — in some cases, even create a new one. This consumes a significant amount of time, especially when many virtual machines are deployed.
With containers, the situation is similar. First, you modify a file (called a Dockerfile) that contains information about the image. You change the lines that specify the OS version. Then the image is rebuilt and pushed to a registry. But that’s not all: the image must then be redeployed. To do this, you use orchestrators — platforms for managing and scaling containers. Orchestration tools (the most well-known are Kubernetes and Docker Swarm) allow automation of these procedures, but developers must install and learn them first.
Deployment Mechanisms
To deploy a single VM, Windows (or Linux) tools will suffice, as will the previously mentioned Hyper-V. But if you have two or more VMs, it’s more convenient to use solutions like PowerShell.
Single containers are deployed from images via a hypervisor (such as Docker), but for mass deployment, orchestration platforms are essential. So in terms of deployment mechanisms, virtualization and containerization are similar: different tools are used depending on how many entities are being deployed.
Data Storage Features
With virtualization, VHDs are used when organizing local storage for a single VM. If there are multiple VMs or servers, the SMB protocol is used for shared file access.
Hypervisors for containers have their own storage tools. For example, Docker has a local Registry repository that lets you create private storage and track image versions. There is also the public Docker Hub repository, which is used for integration with GitHub. Orchestration platforms offer similar tools: for instance, Kubernetes can set up file storage using Azure’s infrastructure.
Load Balancing
To balance the load between VMs, they are moved between servers or even clusters, selecting the one with the best fault tolerance.
Containers are balanced differently. They can’t be moved per se, but orchestrators provide automatic starting or stopping of individual containers or whole groups. This enables flexible load distribution between cluster nodes.
Fault Tolerance
Faults are also handled in similar ways. If an individual VM fails, it’s not difficult to transfer that VM to another server and restart the OS there.
If there’s an issue with the server hosting the containerization platform, containers can be quickly recreated on another server using the orchestrator.
Pros and Cons of Virtualization
Advantages:
Reliable isolation. Logical VM isolation means failures in one VM don’t affect the others on the same server. VMs also offer a good level of network security: if one VM is compromised, its isolation prevents infection of others.
Resource optimization. Several VMs can be deployed on one server, saving on purchasing additional hardware. This also facilitates the creation of clusters in data centers.
Flexibility and load balancing. VMs are easily transferred, making it simpler to boost cluster performance and maintain systems. VMs can also be copied and restored from backups. Furthermore, different VMs can run different OSs, and the kernel can be any type — Linux, Windows, or macOS — all on the same server.
Disadvantages:
Resource consumption. VMs can be several gigabytes in size and consume significant CPU power. There are also limits on how many VMs can run on a single server.
Sluggishness. Deployment time depends on how "heavy" the VM is. More importantly, VMs are not well-suited to scaling. Using VMs for short-term computing tasks is usually not worthwhile.
Licensing issues. Although licensing is less relevant for Russian developers, you still need to consider OS and software licensing costs when deploying VMs — and these can add up significantly in a large infrastructure.
Pros and Cons of Containerization
Advantages:
Minimal resource use. Since all containers share the same OS kernel, much less hardware is needed than with virtual machines. This means you can create far more containers on the same system.
Performance. Small image sizes mean containers are deployed and destroyed much faster than virtual machines. This makes containers ideal for developers handling short-term tasks and dynamic scaling.
Immutable images. Unlike virtual machines, container images are immutable. This allows the launch of any number of identical containers, simplifying testing. Updating containers is also easy — a new image with updated contents is created on the container platform.
Disadvantages:
Compatibility issues. Containers created in one hypervisor (like Docker) may not work elsewhere. Problems also arise with orchestrators: for example, Docker Swarm may not work properly with OpenShift, unlike Kubernetes. Developers need to carefully choose their tools.
Limited lifecycle. While persistent container storage is possible, special tools (like Docker Data Volumes) are required. Otherwise, once a container is deleted, all its data disappears. You must plan ahead for data backup.
Application size. Containers are designed for microservices and app components. Heavy containers, such as full-featured enterprise software, can cause deployment and performance issues.
Conclusion
Having explored the features of virtualization and containerization, we can draw a logical conclusion: each technology is suited to different tasks.
Containers are fast and efficient, use minimal hardware resources, and are ideal for developers working with microservices architecture and application components.
Virtual machines are full-fledged OS environments, suitable for secure corporate software deployment.
Therefore, these technologies do not compete — they complement each other.
10 June 2025 · 7 min to read
Infrastructure
Top RDP Clients for Linux in 2025: Remote Access Tools for Every Use Case
RDP (Remote Desktop Protocol) is a proprietary protocol for accessing a remote desktop. All modern Windows operating systems have it by default. However, a Linux system with a graphical interface and the xrdp package installed can also act as a server. This article focuses on Linux RDP clients and the basic principles of how the protocol works.
Remote Desktop Protocol
RDP operates at the application layer of the OSI model and is based on the Transport Layer Protocol (TCP). Its operation follows this process:
A connection is established using TCP at the transport layer.
An RDP session is initialized.
The RDP client authenticates, and data transmission parameters are negotiated.
A remote session is launched: the RDP client takes control of the server.
The server is the computer being remotely accessed.
The RDP client is the application on the computer used to initiate the connection.
During the session, all computational tasks are handled by the server. The RDP client receives the graphical interface of the server's OS, which is controlled using input devices. The graphical interface may be transmitted as a full graphical copy or as graphical primitives (rectangles, circles, text, etc.) to save bandwidth. By default, RDP uses port 3389, but this can be changed if necessary.
A typical use case is managing a Windows remote desktop from a Linux system. From anywhere in the world, you can connect to it via the internet and work without worrying about the performance of the RDP client.
Originally, RDP was introduced in Windows NT 4.0. It comes preinstalled in all modern versions of Windows. However, implementing a Linux remote desktop solution requires special software.
RDP Security
Two methods are used to ensure the security of an RDP session: internal and external.
Standard RDP Security: This is an internal security subsystem. The server generates RSA keys and a public key certificate. When connecting, the RDP client receives these. If confirmed, authentication takes place.
Enhanced RDP Security: This uses external tools to secure the session, such as TLS encryption.
Advantages of RDP
RDP is network-friendly: it can work over NAT, TCP, or UDP, supports port forwarding, and is resilient to connection drops.
Requires only 300–500 Kbps bandwidth.
A powerful server can run demanding apps even on weak RDP clients.
Supports Linux RDP connections to Windows.
Disadvantages of RDP
Applications sensitive to latency, like games or video streaming, may not perform well.
Requires a stable server.
File and document transfer between the client and server may be complicated due to internet speed limitations.
Configuring an RDP Server on Windows
The most common RDP use case is connecting to a Windows server from another system, such as a Linux client.
To enable remote access, the target system must be configured correctly. The setup is fairly simple and works "out of the box" on most modern Windows editions.
Enable remote desktop access via the Remote Access tab in System Properties.
Select the users who can connect (by default, only administrators).
Check firewall settings. Some profiles like “Public” or “Private” may block RDP by default. If the server is not in a domain, RDP might not work until you allow it manually via Windows Firewall → Allowed Apps.
If behind a router, you might need to configure port forwarding via the router’s web interface (typically under Port Forwarding). Recall that RDP uses TCP port 3389 by default.
Best RDP Clients for Linux
Remmina
Website: remmina.org
Remmina is a remote desktop client with a graphical interface, written in GTK+ and licensed under GPL. In addition to RDP, it supports VNC, NX, XDMCP, SPICE, X2Go, and SSH.
One of its key features is extensibility via plugins. By default, RDP is not available until you install the freerdp plugin. After installing the plugin, restart Remmina, and RDP will appear in the menu.
To connect:
Add a new connection.
Fill in connection settings (you only need the remote machine's username and IP).
Customize further if needed (bandwidth, background, hotkeys, themes, etc.).
Save the connection — now you can connect with two clicks from the main menu.
If you need to run Remmina on Windows, a guide is available on the official website.
FreeRDP
Website: freerdp.com
FreeRDP is a fork of the now-unsupported rdesktop project and is actively maintained under the Apache license.
FreeRDP is a terminal-based client. It is configured and launched entirely via the command line. Its command structure is similar to rdesktop, for example:
xfreerdp -u USERNAME -p PASSWORD -g WIDTHxHEIGHT IP
This command connects to the server at the given IP using the specified credentials and screen resolution.
KRDC
Website: krdc
KRDC (KDE Remote Desktop Client) is the official remote desktop client for KDE that supports RDP and VNC protocols.
It offers a clean and straightforward interface consistent with KDE's Plasma desktop environment.
KRDC is ideal for users of KDE-based distributions like Kubuntu, openSUSE KDE, and Fedora KDE Spin. It integrates well with KDE's network tools and provides essential features such as full-screen mode, session bookmarking, and network browsing via Zeroconf/Bonjour.
KRDC is actively maintained by the KDE community and is available through most Linux package managers.
GNOME Connections
Website: gnome-connections
Vinagre was the former GNOME desktop's default remote desktop client. GNOME Connections, a modernized remote desktop tool for GNOME environments, has since replaced it.
GNOME Connections supports RDP and VNC, providing a simple and user-friendly interface that matches the GNOME design language. It focuses on ease of use rather than configurability, making it ideal for non-technical users or quick access needs.
Features:
Bookmarking for quick reconnections
Simple RDP session management
Seamless integration into GNOME Shell
Connections is maintained as part of the official GNOME project and is available in most distribution repositories.
Apache Guacamole
Website: guacamole.apache.org
This is the simplest yet most complex remote desktop software for Linux.
Simple because it works directly in a browser — no additional programs or services are needed.
Complex because it requires one-time server installation and configuration.
Apache Guacamole is a client gateway for remote connections that works over HTML5. It supports Telnet, SSH, VNC, and RDP — all accessible via a web interface. Although the documentation is extensive, many ready-made scripts exist online to simplify basic setup.
To install:
wget https://git.io/fxZq5 -O guac-install.sh
chmod +x guac-install.sh
./guac-install.sh
After installation, the script will provide a connection address and password.
To connect to a Windows server via RDP:
Open the Admin Panel, go to Settings → Connections, and create a new connection.
Enter the username and IP address of the target machine — that's all you need.
The connection will now appear on the main page, ready for use.
Conclusion
RDP is a convenient tool for connecting to a remote machine running Windows or a Linux system with a GUI. The server requires minimal setup — just a few settings and firewall adjustments — and the variety of client programs offers something for everyone.
09 June 2025 · 6 min to read
Infrastructure
Docker Container Storage and Registries: How to Store, Manage, and Secure Your Images
Docker containerization offers many benefits, one of which is image layering, enabling fast container generation. However, containers have limitations — for instance, persistent data needs careful planning, as all data within a container is lost when it's destroyed. In this article, we’ll look at how to solve this issue using Docker’s native solution called Docker Volumes, which allows the creation of persistent Docker container storage.
What Happens to Data Written Inside a Container
To begin, let’s open a shell inside a container using the following command:
docker run -it --rm busybox
Now let’s try writing some data to the container:
echo "Hostman" > /tmp/data
cat /tmp/data
Hostman
We can see that the data is written, but where exactly? If you're familiar with Docker, you might know that images are structured like onions — layers stacked on top of each other, with the final layer finalizing the image. Each layer can only be written once and becomes read-only afterward. When a container is created, Docker adds another layer for handling write operations.
Since container lifespans are limited, all data disappears once the container is gone. This can be a serious problem if the container holds valuable information. To solve this, Docker provides a solution called Docker Volumes. Let’s look at what it is and how it works.
Docker Volumes
Docker Volumes provide developers with persistent storage for containers. This tool decouples data from the container’s lifecycle, allowing access to container data at any time. As a result, data written inside containers remains available even after the container is destroyed, and it can be reused by other containers. This is a useful solution for sharing data between Docker containers and also enables new containers to connect to the existing storage.
How Docker Volumes Work
A directory is created on the server and then mounted into one or more containers. This directory is independent because it is not included in the Docker image layer structure, which allows it to bypass the read-only restriction of the image layers for containers that include such a directory.
To create a volume, use the following command:
docker volume create
Now, let’s check its location using:
docker volume inspect volume_name
The volume name usually consists of a long alphanumeric string. In response, Docker will display information such as the time the volume was created and other metadata, including the Mountpoint. This line shows the path to the volume. To view the data stored in the volume, simply open the specified directory.
There are also other ways to create a Docker Volume. For example, the -v option can be added directly during container startup, allowing you to create a volume on the fly:
docker run -it --rm -v newdata:/data busybox
Let’s break down what’s happening here:
The -v argument follows a specific syntax, indicated by the colon right after the volume name (in this case, we chose a very creative name, newdata). After the colon, the mount path inside the container is specified. Now, you can write data to this path, for example:
echo "Cloud" > /data/cloud
Data written this way can easily be found at the mount path.
As seen in the example above, the volume name is not arbitrary — it matches the name we provided using -v. However, Docker Volumes also allow for randomly generated names, which are always unique to each host. If you’re assigning names manually, make sure they are also unique.
Now, run the command:
docker volume ls
If the volume appears in the list, it means any number of other containers can use it. To test this, you can run:
docker run -it --rm -v newdata:/data busybox
Then write something to the volume. Next, start another container using the exact same command and you’ll see that the data is still there and accessible — meaning it can be reused.
Docker Volumes in Practice
Now let’s take a look at how Docker Volumes can be used in practice. Suppose we're developing an application to collect specific types of data — let’s say football statistics. We gather this data and plan to use it later for analysis — for example, to assess players’ transfer market values or for betting predictions. Let’s call our application FootballStats.
Preserving Data After Container Removal
Obviously, if we don’t use Docker Volumes, all the collected statistics will simply be lost as soon as the container that stored them is destroyed. Therefore, we need to store the data in volumes so it can be reused later. To do this, we use the familiar -v option:
-v footballstats:/dir/footballstats
This will allow us to store match statistics in the /dir/footballstats directory, on top of all container layers.
Sharing Data
Suppose the FootballStats container has already gathered a certain amount of data, and now it's time to analyze it. For instance, we might want to find out how a particular team performed in the latest national championship or how a specific player did — goals, assists, cards, etc.
To do this, we can mount our volume into a new container, which we’ll call FootballStats-Analytics. The key advantage of this setup is that the new container can read the data without interfering with the original FootballStats container’s ongoing data collection. At the same time, analysis of the incoming data can be performed using defined parameters and algorithms.
This information can be stored anywhere, either in the existing volume or a new one, if needed.
Other Types of Mounts
In addition to standard volumes, Docker Volumes also supports other types of mounts designed to solve specialized tasks:
Bind Mount
Bind mounts are used to attach an existing path on the host to a container. This is useful for including configuration files, datasets, or static assets from websites. To specify directories for mounting into the container, use the --mount option with the syntax <host path>:<container path>.
Tmpfs Mount
Tmpfs mounts serve the opposite purpose of regular Docker Volumes — they do not persist data after the container is destroyed. This can be useful for developers who perform extensive logging. In such cases, continuously writing temporary data to disk can significantly degrade system performance. The --tmpfs option creates temporary in-memory directories, avoiding constant access to the file system.
Drivers
Docker Volume Drivers are a powerful tool that enable flexible volume management. They allow you to specify various storage options, the most important being the storage location — which can be local or remote, even outside the physical or virtual infrastructure of the provider. This ensures that data can survive not only the destruction of the container but even the shutdown of the host itself.
Conclusion
So, we’ve learned how to create and manage storage using Docker Volumes. For more information on how to modify container storage in Docker, refer to the platform’s official documentation.
09 June 2025 · 6 min to read
Do you have questions,
comments, or concerns?
Our professionals are available to assist you at any moment,
whether you need help or are just unsure of where to start.
whether you need help or are just unsure of where to start.
