You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I had the same problem; it seems apt-get update isn't guaranteed to run before the packages are installed, causing a fail due to outdated packages. What works for me is to do a vagrant up and then run provisioning again (because apt-get update ran at some point, just not in the right order) with vagrant reload --provision. Ensuring the command is run first should solve the issue.
I get this everytime no matter what I try:
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!
puppet apply --modulepath '/tmp/vagrant-puppet-3/modules-0:/etc/puppet/modules' --manifestdir /tmp/vagrant-puppet-3/manifests --detailed-exitcodes /tmp/vagrant-puppet-3/manifests/init.pp
Stdout from the command:
Stderr from the command:
stdin: is not a tty
Could not parse for environment production: Could not match
/usr/bin/
, at /tmp/vagrant-puppet-3/manifests/init.pp:2 on nodeThe text was updated successfully, but these errors were encountered: