Category: swarm

Learning – Docker Swarm Network Drivers

Learning - Docker Swarm Network Drivers


The default network driver. Needs to map the port to host in order to access port of container.


Removes network isolation between the container and the Docker host, and uses the host's networking directly. So the containers can not have port conflicting with other containers and also host.

The IP will be the same as host.


Disables all networking for containers. Usually used in conjunction with a custom network drive.


Connect multiple Docker daemons together and enable swarm services to communicate with each other daemons.

Using this overlay network, the container on different hosts can communicate with each other.


Allow you to assign a MAC address to a container, making it appears as a physical device on the network. The Docker daemon routes traffic to container by their MAC addresses.

This allows container has different IP address on the host network.

Selection of container orchestration platform

Selection of container orchestration platform

I'm trying to manage my docker containers using container orchestration platform. There are a few of them can be used.


Docker Swarm

Easy to setup and manage existing docker machines.

Kubernetes (K8s)

Widely used.


K3s is Rancher’s k3s Kubernetes distro, lightweight, single binary, and low resource usage.




Unlike company environments, most of my docker containers applications have individual database. The application usage is low, autoscaling isn't a requirement for me but the backup and restore is important.


k8s vs k3s
Docker Swarm vs Kubernetes: how to choose a container orchestration tool