@tzz

@Silex since you could be dealing with multiple daemons across multiple machines, maybe something like this would make sense:

(with-docker-daemon mydaemon
(docker-image-pull ...))
Without the with-docker-daemon wrapper, all the operations then implicitly work on the local Docker daemon, as users would expect.

It's unclear what happens if you take an image from one daemon and hand it to another. Maybe across daemons, the image is serialized as just a string... and other things are just not portable, like running processes, but could again be serialized to strings.

Could you please consider also supporting Tramp syntax somehow? It would be ridiculously useful to me to be able to use Docker remotely over Tramp/SSH. I don't have a strong opinion on the syntax but something like /user@host:/var/docker/docker.sock could be good enough.

https://github.com/emacs-pe/docker-tramp.el calls shell commands remotely, while access to the actual API would be much more reliable and scalable.

Do we want to make some kind of OO api?

For example:

(let ((images (docker-images))
      (first-image (car images)))
  (docker-image-pull first-image)
  (docker-image-push first-image "Foo:bar")
  (docker-image-rmi first-image))

With eieio methods for each api (pull/push/etc).

Inspiration: https://github.com/swipely/docker-api

Right now the options to configure the docker connection is tightly coupled to how make-network-process works, which has an API kinda bizarre and unintuitive.

Refactor the options so it parses ONE url instead, like:

(setq docker-connection-url "file:///var/docker/docker.sock")
(setq docker-connection-url "http://somehost.com:1234")