Vagrant plugin issues

[SAKSHAM CHITRANSH]

This error is showing while installing a machine what should i do?

[dnmo...@gmail.com]

You're going to need to post your Vagrant file.

[SAKSHAM CHITRANSH]

# -- 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 = "ubuntu/focal64"

  # 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.56.82"

  # 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 = "2048"
   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
  # Ansible, Chef, Docker, Puppet and Salt are also available. Please see the
  # documentation for more information about their specific syntax and use.
   config.vm.provision "shell", inline: <<-SHELL
   sudo apt-get update
   sudo apt-get install \
    ca-certificates \
    curl \
    gnupg -y

sudo install -m 0755 -d /etc/apt/keyrings
curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo gpg --dearmor -o /etc/apt/keyrings/docker.gpg
sudo chmod a+r /etc/apt/keyrings/docker.gpg
echo \
  "deb [arch="$(dpkg --print-architecture)" signed-by=/etc/apt/keyrings/docker.gpg]   https://download.docker.com/linux/ubuntu \
  "$(. /etc/os-release && echo "$VERSION_CODENAME")" stable" | \
  sudo tee /etc/apt/sources.list.d/docker.list > /dev/null
  sudo apt-get update
  sudo apt-get install docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-      plugin -y
   SHELL
end

this is the vagrant file and it is showing package plugin error what should i do?

--
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/hashicorp/vagrant/issues
Discuss: https://discuss.hashicorp.com/c/vagrant/24
---
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/22a16ce0-8b7d-4099-b0e1-885e36d406b7n%40googlegroups.com.

[dnmo...@gmail.com]

In your Vagrant file, you are using the SHELL provider. The way that it works is each line is run sequentially.. e.g.

  config.vm.provision "shell", inline: <<-SHELL
   sudo apt-get update
   sudo apt-get install \
    ca-certificates \

...

The snippet above each new line is marked by a \

You are missing those \ lines on the remainder of your Shell Script work which is likely the issue. 

This is also weird looking  sudo apt-get install docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-      plugin -y

It looks like there are some extra spaces there as well

[Jim McGinness]

Without knowing where you copied this vagrantfile from, I'd guess there should be no space between "docker-compose-"    and   "plugin -y"

To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/CAL%3DXiL94S8ynBqMvFv%2By6HFUKN8H-%2BnQYXV_B1TkSrJ7vY6WtQ%40mail.gmail.com.

[Alvaro Miranda Aguilera]

Hello

The error message is complaining about plugin

so you need to make sure the shell part is a valid script

it seem the formatting is wrong around this line

  sudo apt-get install docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-      plugin -y

i think should be

  sudo apt-get install docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-plugin -y

Better will be make sure you are using a good / valid Vagrantfile, go and check as possible a copy of the file from where you got this

if this is from a book, try to get the commands they want you to run