Vagrant box available for Snappy Ubuntu Core

[Ross Duggan]

Yes, it looks like updating the OS nukes the vagrant user and guest
additions (in retrospect, I might have anticipated this). As it is, the
docker user already exists on the base system before the docker app is
installed.

Someone who understands snappy's internals might have suggestions for a
workaround (other than "don't update the core system)" but I suspect we'll
be waiting until an official box is produced for that.

On Fri, Dec 12, 2014 at 2:58 AM, Kevin Glavin <archen.sol at gmail.com> wrote:

> using duggan/ubuntu-core-alpha, after running `snappy update && sudo
> reboot` within the VM, `vagrant ssh` no longer works. It looks like
> /home/vagrant/.ssh/authorized_keys and /etc/ssh/sshd_config are all intact.
> Anyone else experiencing this?
>
> On Wed, Dec 10, 2014 at 7:44 PM, Ross Duggan <ross.duggan at acm.org> wrote:
>>
>> I've a VirtualBox one up on VagrantCloud (mentioned in snappy-dev but
>> probably as useful here).
>>
>> https://atlas.hashicorp.com/duggan/boxes/ubuntu-core-alpha
>>
>> Includes Guest Additions for shared folder access.
>>
>> `vagrant init duggan/ubuntu-core-alpha` and `vagrant up` should get you
>> going.
>>
>> On Wed, Dec 10, 2014 at 11:19 PM, Stelian Iancu <reg at iancu.ch> wrote:
>>
>>> Hi all,
>>>
>>> I've created and uploaded a Vagrant box for Snappy. At the moment it's
>>> only for VMware Fusion on the Mac.
>>>
>>> In order to use it, create a new folder on your machine and inside
>>> create a Vagrantfile with the following contents:
>>>
>>> VAGRANTFILE_API_VERSION = "2"
>>>
>>> Vagrant.configure(VAGRANTFILE_API_VERSION) do |config|
>>>   config.vm.box = "siancu/ubuntu-core-alpha-01"
>>>   config.ssh.username = "ubuntu"
>>>   config.ssh.password = "ubuntu"
>>> end
>>>
>>> Save it and then run the following command:
>>>
>>> vagrant up --provider vmware_fusion
>>>
>>> After the machine boots up, do a vagrant ssh and you should be in!
>>>
>>> Note that the following error message is displayed after booting up:
>>>
>>> ——————————————————————————————————————————
>>> The following SSH command responded with a non-zero exit status.
>>> Vagrant assumes that this means the command failed!
>>>
>>> su -c 'cat /tmp/vagrant-network-interfaces > /etc/network/interfaces'
>>>
>>> Stdout from the command:
>>>
>>> Stderr from the command:
>>>
>>> stdin: is not a tty
>>> bash: /etc/network/interfaces: Read-only file system
>>> ——————————————————————————————————————————
>>>
>>> As far as I can tell, it can be ignored.
>>>
>>> If somebody has a Windows machine with VMware workstation installed,
>>> please try
>>> vagrant up --provider vmware_workstation
>>> or
>>> vagrant up --provider vmware_desktop
>>> maybe it works :-).
>>>
>>> At the moment there's no VirtualBox version of this box, I might make
>>> one in the future.
>>>
>>> Let me know what you think.
>>>
>>> Thanks,
>>> Stelian
>>>
>>> --
>>> snappy-app-devel mailing list
>>> snappy-app-devel at lists.ubuntu.com
>>> Modify settings or unsubscribe at:
>>> https://lists.ubuntu.com/mailman/listinfo/snappy-app-devel
>>>
>>>
>>
>> --
>> snappy-app-devel mailing list
>> snappy-app-devel at lists.ubuntu.com
>> Modify settings or unsubscribe at:
>> https://lists.ubuntu.com/mailman/listinfo/snappy-app-devel
>>
>>
>
> --
> Kevin Glavin
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/snappy-app-devel/attachments/20141212/2b23eba7/attachment-0001.html>