Docker vs XBPS (X Binary Package System)

Docker creates a single object, containing an application with its dependencies, that can be moved between any docker-enabled machines, guaranteeing the same environment for application execution.

Docker tracks changes in systems. It allows for commits and rollbacks and for quick deployment due to having to deploy only the updated code.

Docker essentially allows creating boilerplate systems (a LAMP stack, for example) that can be used as a starting point on multiple projects. And you can find multiple such containers already created by people in their public registry.

Allows automatically assembling a container from its source code.

Docker allows easily pushing and pulling containers to and from their public index.docker.io registry. Additionally, dotCloud maintains a list of official repositories of the more popular containers.

You can set up Docker within an already virtualized environment such as a virtual machine. This allows you to run Docker on Mac and Windows, among other use-cases.

Docker can be used with OpenVZ, systemd-nspawn, libvirt-lxc, libvirt-sandbox, qemu/kvm, BSD Jails, Solaris Zones, and chroot.

XBPS can detect incompatible shared libraries or dependencies and gives you options before installing.

When installing software you can choose to install binaries or build it from source (natively or cross-compiled).

XBPS can not only be used for installing/removing packages, but it can query for package info (such as version, dependencies, size etc), reconfigure packages, report and fix issues by modifying the package database, search for alternatives, manage local repositories and various other useful tools.