'vagrant up' or 'vagrant ssh' problem

[Robert Werk]

I have installed the vagrant 2.0.0 with VirtualBox 5.1.30. I have run 'vagrant init' in the directory "Shell Udacity" and the 'VagrantFile' is there. I run 'vagrant up' then 'vagrant ssh' the attached image is below of what the outputs. I have no idea what to even ask right now. 

[Alvaro Miranda Aguilera]

hello

whats the generated Vagrantfile?

vagrant init <user/box> should be the proper format, like hashicorp/precise64

if you did vagrant init without argument, then you need to update the box manually

Alvaro

On Mon, Oct 30, 2017 at 5:14 PM, Robert Werk <werk...@gmail.com> wrote:

I have installed the vagrant 2.0.0 with VirtualBox 5.1.30. I have run 'vagrant init' in the directory "Shell Udacity" and the 'VagrantFile' is there. I run 'vagrant up' then 'vagrant ssh' the attached image is below of what the outputs. I have no idea what to even ask right now. 

--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
---
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vagrant-up+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/25b615cb-6a40-40ea-8c19-ac8b8a30fc1c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Alvaro

[Robert Werk]

This is the file that the Udacity course I was taking said to download. The one created upon use of 'vagrant int' is much longer and below the one downloaded from the Udacity course. This file is formatted as a ".dms". 

# -*- mode: ruby -*-

# vi: set ft=ruby :

# Vagrantfile API/syntax version. Don't touch unless you know what you're doing!

VAGRANTFILE_API_VERSION = "2"

# Installation script

$script = <<SCRIPT

echo Provisioning system ...

apt-get install cowsay unzip

rm /usr/share/cowsay/cows/*odo*

SCRIPT

Vagrant.configure(VAGRANTFILE_API_VERSION) do |config|

  config.vm.box = "ubuntu/trusty64"

  config.vm.provision "shell", inline: $script

end

This is what gets created just running the 'vagrant init' command.

# -*- mode: ruby -*-

# vi: set ft=ruby :

# All Vagrant configuration is done below. The "2" in Vagrant.configure

# configures the configuration version (we support older styles for

# backwards compatibility). Please don't change it unless you know what

# you're doing.

Vagrant.configure("2") do |config|

  # The most common configuration options are documented and commented below.

  # For a complete reference, please see the online documentation at

  # https://docs.vagrantup.com.

  # Every Vagrant development environment requires a box. You can search for

  # boxes at https://vagrantcloud.com/search.

  config.vm.box = "base"

  # Disable automatic box update checking. If you disable this, then

  # boxes will only be checked for updates when the user runs

  # `vagrant box outdated`. This is not recommended.

  # config.vm.box_check_update = false

  # Create a forwarded port mapping which allows access to a specific port

  # within the machine from a port on the host machine. In the example below,

  # accessing "localhost:8080" will access port 80 on the guest machine.

  # NOTE: This will enable public access to the opened port

  # config.vm.network "forwarded_port", guest: 80, host: 8080

  # Create a forwarded port mapping which allows access to a specific port

  # within the machine from a port on the host machine and only allow access

  # via 127.0.0.1 to disable public access

  # config.vm.network "forwarded_port", guest: 80, host: 8080, host_ip: "127.0.0.1"

  # Create a private network, which allows host-only access to the machine

  # using a specific IP.

  # config.vm.network "private_network", ip: "192.168.33.10"

  # Create a public network, which generally matched to bridged network.

  # Bridged networks make the machine appear as another physical device on

  # your network.

  # config.vm.network "public_network"

  # Share an additional folder to the guest VM. The first argument is

  # the path on the host to the actual folder. The second argument is

  # the path on the guest to mount the folder. And the optional third

  # argument is a set of non-required options.

  # config.vm.synced_folder "../data", "/vagrant_data"

  # Provider-specific configuration so you can fine-tune various

  # backing providers for Vagrant. These expose provider-specific options.

  # Example for VirtualBox:

  #

  # config.vm.provider "virtualbox" do |vb|

  #   # Display the VirtualBox GUI when booting the machine

  #   vb.gui = true

  #

  #   # Customize the amount of memory on the VM:

  #   vb.memory = "1024"

  # end

  #

  # View the documentation for the provider you are using for more

  # information on available options.

  # Enable provisioning with a shell script. Additional provisioners such as

  # Puppet, Chef, Ansible, Salt, and Docker are also available. Please see the

  # documentation for more information about their specific syntax and use.

  # config.vm.provision "shell", inline: <<-SHELL

  #   apt-get update

  #   apt-get install -y apache2

  # SHELL

end

Is there a way to make the upper one work?

Thanks,

Rob

On Monday, October 30, 2017 at 5:49:30 PM UTC-4, Alvaro Miranda Aguilera wrote:

hello

whats the generated Vagrantfile?

vagrant init <user/box> should be the proper format, like hashicorp/precise64

if you did vagrant init without argument, then you need to update the box manually

Alvaro

On Mon, Oct 30, 2017 at 5:14 PM, Robert Werk <werk...@gmail.com> wrote:

I have installed the vagrant 2.0.0 with VirtualBox 5.1.30. I have run 'vagrant init' in the directory "Shell Udacity" and the 'VagrantFile' is there. I run 'vagrant up' then 'vagrant ssh' the attached image is below of what the outputs. I have no idea what to even ask right now. 

--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
---
You received this message because you are subscribed to the Google Groups "Vagrant" group.

To unsubscribe from this group and stop receiving emails from it, send an email to vagrant-up+...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/25b615cb-6a40-40ea-8c19-ac8b8a30fc1c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Alvaro

[Alvaro Miranda Aguilera]

Hello

The vagrantfile you did share is missing some commands, so I would suggest fix it and see how to share feedback

# -*- mode: ruby -*-

# vi: set ft=ruby :

# Vagrantfile API/syntax version. Don't touch unless you know what you're doing!

VAGRANTFILE_API_VERSION = "2"

# Installation script

$script = <<SCRIPT

echo Provisioning system ...

export DEBIAN_FRONTEND=noninteractive

apt-get update

apt-get install -y cowsay unzip

rm /usr/share/cowsay/cows/*odo*

SCRIPT

Vagrant.configure(VAGRANTFILE_API_VERSION) do |config|

  config.vm.box = "ubuntu/trusty64"

  config.vm.provision "shell", inline: $script

end

alvaro