Relationship between snaps and containers, if any

Gustavo Niemeyer gustavo.niemeyer at
Wed Jan 25 14:13:05 UTC 2017

Interesting.. I actually don't see that line between snaps and Docker.
Just like you can run "docker run mysql" several times, one may run
"mysnap.mysql" several times. In both cases the daemon will be visible to
the external world via a separate port of the local host's public IP
address. In both cases mysql will be isolated from the local environment by

It's even a bit more convenient to do that using a snap. Easier to manage
the process on a systemd unit, for example, since the mysql process will
indeed be a child of systemd/etc instead of a child of the docker daemon.

On Wed, Jan 25, 2017 at 11:51 AM, Mark Shuttleworth <mark at> wrote:

> The best way to think of this is to know that snaps are GREAT when you
> have a precise 1:1 relationship between "machines" and "running
> instances". And Docker is GREAT when you want an elastic relationship.
> So for example, if you want a MySQL "appliance" on a device, there will
> only ever be 1 MySQL instance on that device, you want a snap. If you
> want a cluster where there may be 1-many instances of MySQl on each
> actual machine or VM, then you want Docker.
> The reason for this is that Docker gives each running process its own IP
> address. That's perfect for the hyper-elastic case - each extra MySQSL
> is just another IP address to talk to. But if you have a machine where
> you already have an IP address and all you want is a MySQL there then a
> snap will be easier.
> This is why a snap of the Docker daemon makes such sense - in your
> cluster, you want exactly one copy of Docker itself running on each
> machine, and that is best pulled in as  a snap. That docker process then
> manages an arbitrary number of docker processes on each machine.
> Make sense?
> Mark
> --
> Snapcraft mailing list
> Snapcraft at
> Modify settings or unsubscribe at:
> an/listinfo/snapcraft

gustavo @
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the Snapcraft mailing list