Back to articles
DevOps & Systems

Complete Guide to Configure Podman to Replace Docker Desktop on Ubuntu VPS Development

Podman is a modern containerization tool compatible with Docker, enabling container execution without a background daemon, ideal for Ubuntu VPS development environments. This guide...

DPTCloud Engineering6 min read
Complete Guide to Configure Podman to Replace Docker Desktop on Ubuntu VPS Development

Image credit: 422737 · Pixabay Content License

Podman is a modern containerization tool compatible with Docker, enabling container execution without a background daemon, ideal for Ubuntu VPS development environments. This guide provides step-by-step instructions to fully replace Docker Desktop with Podman, covering installation, network configuration, container management, and integration with common development tools such as Nginx, Node.js, and PostgreSQL. With Podman, you can maintain high performance, strong security, and easy container management on Ubuntu VPS without the overhead of Docker Desktop. This guide is tailored for developers using VPS environments where system resources are limited and process simplification is essential.

Why Choose Podman Over Docker Desktop?

Podman is an open-source containerization tool developed by Red Hat, operating similarly to Docker but without a background daemon. This reduces system load, enhances security, and simplifies container management. On Ubuntu VPS, Podman performs more efficiently than Docker Desktop because it requires no additional software, does not need full root privileges, and integrates well with systemd. Podman supports all Docker commands, making migration straightforward. For development applications like Node.js, Python, or databases, Podman offers a flexible, secure, and efficient container environment compared to Docker Desktop.

Install Podman on Ubuntu VPS

To begin, update your system and install Podman. On Ubuntu 22.04 or 20.04, follow these steps:

sudo apt update
sudo apt install -y podman

After installation, verify the Podman version to confirm success:

podman --version

Podman is now ready to use. To fully replace Docker Desktop, configure Podman to function as a daemonless container engine. While Podman does not require a daemon, you can use podman system service to create a REST interface similar to Docker if needed:

podman system service --time=10 &

Install podman-docker for full Docker CLI compatibility:

sudo apt install -y podman-docker

Configure Network and Storage for Podman

Podman uses host networking by default, but you can create isolated networks for containers. Create a new network:

podman network create dev-network

For data storage, use volumes or bind mounts. For example, create a volume for PostgreSQL:

podman volume create postgres-data
podman run -d --name postgres -e POSTGRES_PASSWORD=secret -v postgres-data:/var/lib/postgresql/data postgres

For web applications, run Nginx in a container and map ports:

podman run -d -p 80:80 --name nginx -v /path/to/website:/usr/share/nginx/html nginx

Podman supports Docker-like commands such as podman run, podman ps, podman stop, and podman logs. Use podman ps -a to view all running containers.

Integrate with Development Tools

To integrate Podman into your development workflow, use common tools like Node.js, Python, or PostgreSQL. For example, run a Node.js application in a container:

podman run -d -p 3000:3000 --name node-app -v $(pwd):/app node:18 npm start

For databases, use PostgreSQL or MySQL in containers. With PostgreSQL:

podman run -d --name db -e POSTGRES_PASSWORD=secret -p 5432:5432 postgres

To manage multiple containers, use podman-compose, a Docker Compose alternative:

podman-compose up -d

Install podman-compose:

sudo pip3 install podman-compose

Testing and Maintenance

After configuration, verify container operation:

podman ps
podman logs <container-id>

To stop a container:

podman stop <container-id>

To remove a container:

podman rm <container-id>

Podman automatically manages inactive containers. Configure automatic cleanup with:

podman system prune -a

Troubleshooting and Tips

If you encounter permission issues, ensure your user has access to /var/lib/containers. If needed, add the user to the podman group:

sudo usermod -a -G podman <username>

For network issues, verify the network is created correctly:

podman network ls

To view detailed container information:

podman inspect <container-id>

Podman supports various configuration options, including podman run --rm to automatically remove containers after execution.

References

For more information on Podman, consult the official documentation: https://podman.io/. This guide is based on Podman configuration principles on Ubuntu, compatible with development environments on VPS. Tools like Nginx, Node.js, and PostgreSQL can be easily integrated with Podman to create a flexible and efficient development environment.

Podman vs Docker Desktop Comparison

Below is a comparison between Podman and Docker Desktop on Ubuntu VPS:

Feature Podman Docker Desktop
Background Daemon Not required Required
Root Privileges Required Not required Required
Docker CLI Compatibility Yes (via podman-docker) Direct
Performance on VPS More efficient Less efficient
Container Management Simpler, no daemon More complex

Prerequisites and Verification

Before starting, ensure you have:

  • Ubuntu 20.04 or 22.04
  • Updated software
  • Sudo privileges

After installation, verify with:

podman --version

If the command returns a version number, installation is successful.

Customization and Configuration

Podman supports customization via configuration files. For example, create ~/.config/containers/containers.conf:

[containers]
runtime = "runc"
[engine]
cgroup_manager = "cgroupfs"

Adjust settings to match your development environment.

Run a Real-World Application

Run a Node.js app with Nginx and PostgreSQL:

podman run -d --name nginx -p 80:80 -v /path/to/website:/usr/share/nginx/html nginx
podman run -d --name node-app -p 3000:3000 -v $(pwd):/app node:18 npm start
podman run -d --name db -e POSTGRES_PASSWORD=secret -p 5432:5432 postgres

To test, visit http://localhost:80 and http://localhost:3000.

Alternative Solutions

If Podman is not suitable, consider alternatives such as NVMe Cloud VPS for Docker, Nginx & Databases or High-Performance Dedicated Servers for Production Clusters.

To learn more about automated data integration, see Managing Automated Data Integration for Data Engineers with Apache Hop on Cloud VPS.

To learn more about web system migration, see Web System Migration Journey from AWS to Hetzner with Coolify: Secrets to Optimize 85% Costs for Enterprises.

DPTCloud Tier III Infrastructure

Recommended NVMe Cloud VPS Plans to Deploy This Setup

Enterprise RAID 10 NVMe SSDs, CMC & FPT District 9 uplinks with Anycast Anti-DDoS and 99.99% SLA.

View 22 VPS Plans
ECO · vn-02

VPS-2E

94.600 ₫ / mo

10% VAT included

  • CPU: 2 vCPU
  • RAM: 2 GB
  • SSD: 30 GB NVMe
ECO · vn-02Recommended

VPS-3E

170.500 ₫ / mo

10% VAT included

  • CPU: 2 vCPU
  • RAM: 4 GB
  • SSD: 50 GB NVMe
BASIC · vn-01Recommended

VPS-05

457.600 ₫ / mo

10% VAT included

  • CPU: 4 vCPU
  • RAM: 8 GB
  • SSD: 50 GB NVMe

Related Articles

View all
ZaloZalo SupportDiscord0384 753 478