Relationship between snaps and containers, if any

Gustavo Niemeyer gustavo.niemeyer at
Thu Jan 26 13:55:55 UTC 2017

It seems that the most common way to deploy Docker is by mapping ports out
of the private IP addresses into the local host's public IP, which means
it's completely analogous to multiple processes in the same host. Even when
assigning the docker container to an external IP, a commonly recommended
practice is to use -p <public ip>:<public port>:<internal port>, which
means the public IP is sitting on the external host. E.g.:

That also maps exactly to just asking the process bind to the particular IP.

On Thu, Jan 26, 2017 at 11:12 AM, Mark Shuttleworth <mark at> wrote:

> Well, from an *external* point of view, all the docker mysql processes
> are the same, on the same port, just with different IP addresses. That's
> the very nice property of docker for "hyper-elastic" workloads. I don't
> think snaps will be useful in that context, unless snaps find a way to
> live inside docker containers, but that's OK since snaps are useful in
> other contexts.
> 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