.box refresh needed?

[TheNotary]

I did a vagrant up and vagrant ssh and ran into this:

More outputs at the end of the vagrant up:

==> default: --:--:-- --:--:--  4758
==> default: Cloning Oh My Zsh...
==> default: Cloning into '/home/vagrant/.oh-my-zsh'...
==> default: Looking for an existing zsh config...
==> default: Using the Oh My Zsh template file and adding it to ~/.zshrc
==> default: Time to change your default shell to zsh!
==> default: Password: 
==> default: chsh: PAM: Authentication failure
==> default: -----> Customizing .zshrc
==> default: Password: 
==> default: Running provisioner: shell...
    default: Running: /tmp/vagrant-shell20170521-26057-u66nvg.sh
==> default: -----> Using Sixarm git config
==> default: Cloning into '/tmp/sixarm-gitconfig'...
==> default: Running provisioner: shell...
    default: Running: /tmp/vagrant-shell20170521-26057-1anolak.sh
==> default: -----> Installing mumble chat server
==> default: E: Could not open lock file /var/lib/dpkg/lock - open (13: Permission denied)
==> default: E: Unable to lock the administration directory (/var/lib/dpkg/), are you root?
==> default: -----> Configuring mumble chat server
==> default: debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied
==> default: debconf: DbDriver "config": could not write /var/cache/debconf/config.dat-new: Permission denied
==> default: cp: cannot create regular file '/etc/mumble-server.ini': Permission denied
==> default: Failed to restart mumble-server.service: Interactive authentication required.
==> default: See system logs and 'systemctl status mumble-server.service' for details.
The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
went wrong.

Disclaimer: There's a slight chance I just don't know how to use zsh =/

[begriffs]

That's definitely unexpected behavior. Looks like some of the installation steps are expecting root privileges. I think the user differs between when running this locally vs on a provider like digital ocean. Can you try adding some "sudo" into the scripts and trying again?

[begriffs]

In fact looks related to #5. I always use this pairing image on a public server as described here so I don't run into the type of errors you report, but I agree that we should fix that case also.