Developer Target for Snappy

Dustin Kirkland kirkland at
Wed Jan 7 23:23:50 UTC 2015

On Wed, Jan 7, 2015 at 4:23 PM, Ben Howard <ben.howard at> wrote:
> In looking at the problems with creating VM images for developers, there are
> a large number that use Virtualbox (i.e Vagrant) or VMware Fusion on their
> shiny Macs. About a year ago we released Vagrant images that quickly became
> extremely popular, with over 1M downloads.
> While working on enabling VMware and Virtualbox, it became apparent that we
> run a real risk of having a dozen downloads if we are not careful. What I
> would like to propose is that we have the standard "core", "cloud", and a
> "developer" image.
> The idea behind the developer image is that we would put all the stuff that
> makes development easy and target the "non-production" environments.
> My initial proposed requirements are:
> SSH enabled by default
> Vagrant user defined
> /home/vagrant exists
> password is locked
> defined a sudoer
> Packages installed:
> open-vm-tools
> virtualbox-dkms modules pre-built
> virtualbox-guest-utils
> ssh-import-id

+1 on all of the above, for a developer environment.

The other thing that personally, I'd like, to feel a bit more
comfortable when using Snappy in a remote cloud when doing
development, would be Byobu*, so that my state and work can be
preserved in a running session, in case I get disconnected, or if I
want to share that environment with a colleague.

*Full disclosure: I'm the maintainer of Byobu, and kind of like to run
it everywhere, anyway :-)

More information about the snappy-devel mailing list