What's the difference between docker.io and docker?

35

5

Trying to learn docker here but I am a bit confused on what the difference is between docker.io and docker. Is docker.io the daemon server and docker the client? Why does the daemon need to run all the time?

Pithikos

Posted 2014-07-17T08:28:28.300

Reputation: 984

Answers

12

docker-io is the deb package name used by Ubuntu distribution docker-engine is the deb package name from the official Docker Ubuntu distribution.

Probably you want docker-engine because the Ubuntu one is too old and buggy to be used. As of today Ubuntu has 1.6.2 and Docker registry has 1.12.0 !

In terms of Docker, 1.6.2 counts as stone-age.

sorin

Posted 2014-07-17T08:28:28.300

Reputation: 9 439

4The difference seems to have narrowed now in Xenial: Ubuntu's docker.io 1.12.3 vs Docker's docker-engine 1.13.1. – Pierz – 2017-02-20T16:47:04.680

@Pierz but will ubuntu upgrade within the same release? Before 18.04 the difference will probably widen again ;) – nafg – 2017-03-02T03:43:28.337

3one year later, "mind the gap": the versions available via docker(.com) vs the ubuntu pkg repo is now so wide it's hard to even compare (as of mid-2017, ubuntu 17.04 (zesty)). What was called docker-engine from docker.com is now split into docker-ce and docker-ee (a free "community edition" & paid "enterprise edition", respectively), and docker-compose must be installed either from git or via pip install docker-compose to get the correct, corresponding latest version. Presently, sadly, one must simply avoid ubuntu repos for all things docker. – michael – 2017-07-30T23:30:23.223

11

If you are using Ubuntu, and you do an

sudo apt-get install docker

You will get a package described as a "System tray for KDE3/GNOME2 applications"

If on the other hand, you do

sudo apt-get install docker.io

You will get a package described as "Docker complements kernel namespacing with a high level API which operates at the process level." i.e. the Docker everyone is usually thinking about when they say Docker.

peteshaw

Posted 2014-07-17T08:28:28.300

Reputation: 121

This doesn't answer the question. – Toto – 2017-12-01T14:23:34.480

1How does this answer the question, i.e. "what's the difference ...?"? – Pierre.Vriens – 2017-12-01T14:42:27.560

@peteshaw: typo Sytem => System – pevik – 2018-01-08T10:35:44.970

4this answered my question, because I was confused that apt-get install docker on ubuntu 18.04 didnt't gave me the docker application and I looked what the difference between those two is (apt-cache search ^docker would have told me that, too) – eli – 2018-05-09T08:26:11.347

5The answer is that docker is a tray plugin, while docker.io is the Docker containerization software. Ubuntu already had a package called docker so they had to call the package for the Docker container software docker.io – theferrit32 – 2018-11-27T03:39:35.997

2This is the best answer as it actually tells you that if you want to install the container software, you should use sudo apt-get install docker.io – JacKeown – 2019-05-01T20:57:58.647

Also, this heads up: the snap is called docker. Therefore, sudo snap install docker and sudo apt install docker.io both install the container system called docker, but sudo apt install docker will install the system tray called docker. The docker dpkg is actually a transitional package for wmdocker, so perhaps the naming will eventually be made less confusing. – Reece – 2020-01-23T18:04:15.097

7

Docker is the name of the open platform for developers and sysadmins to build, ship, and run distributed applications. Docker.io on the other hand is the name of the package that you install in your Linux OS (i.e. Ubuntu). See this link here.

In terms of how it works, the Docker Engine consists of two parts: a daemon, a server process that manages all the containers, and a client, which acts as a remote control for the daemon. I would suggest you to try a quick demo they have on their site, located here.

From a usability standpoint, you invoke the Docker client anytime you use the docker command.

dandaman12

Posted 2014-07-17T08:28:28.300

Reputation: 837

4Yes, but that doesn't say anything about the two different processes, namely docker and docker.io – Pithikos – 2014-07-18T15:30:13.517

4

It seems docker is just a symbolic link to docker.io:

> file $(which docker)
/usr/local/bin/docker: symbolic link to `/usr/bin/docker.io'

So we can assume that docker.io is both the daemon and the client process, just invoked with different flags I assume?!

Pithikos

Posted 2014-07-17T08:28:28.300

Reputation: 984

That's it exactly. docker.io uses the same binary for both client and server/daemon. – Rob Wells – 2016-04-17T15:22:41.570

3

Talking about Debian packages: docker.io is the name of the package provided by Debian/Ubuntu, while docker is the name of the package provided by docker.com.

Technically, these packages are built differently: for docker.io the build dependencies are fetched from Debian packages, while for docker, the build dependencies are in-tree, in the vendor directory.

If you want more details, I wrote a detailed blog post at: https://www.collabora.com/news-and-blog/blog/2018/07/04/docker-io-debian-package-back-to-life/

elboulangero

Posted 2014-07-17T08:28:28.300

Reputation: 131