When I try to launch a new development environment running Ubunut in virtualbox I save my framework to a directory in Sites on my mac, then open terminal and cd to the directory with the Vagrantfile before running "vagrant up". After an initial start I get several errors that end in the environment not starting. The error is:
The following packages have unmet dependencies:
libapache2-mod-php5 : Depends: apache2-api-20120211 but it is not installable. PreDepends: apache2 (>= 2.4)
When I try to upgrade the PPA, for example running the code:
sudo add-apt-repository ppa:ondrej/php5
sudo apt-get update
I get the error that add-apt and/or get-app command not found! I do not know what to do.
Vagrantfile and Provision script
Related
install both vagrant and vmware via homebrew
brew install --cask vagrant
brew install --cask vmware-fusion
verify that everything is installed
➜ ~ vmrun -T ws list
Total running VMs: 0
➜ ~ vagrant -v
Vagrant 2.3.0
set the default provider as vmware_desktop in my .zshrc (and "sourced" it)
export VAGRANT_DEFAULT_PROVIDER=vmware_desktop
initialize a folder and add a box following official get started
vagrant init hashicorp/bionic64
vagrant box add hashicorp/bionic64
and select the option 3) vmware_desktop
finally run vagrant up from the initialised folder and observe the error
The provider 'vmware_desktop' could not be found, but was requested to
back the machine 'default'. Please use a provider that exists.
Vagrant knows about the following providers: docker, hyperv, virtualbox
did I make some mistake in the setup
You miss to install the Vagrant VMWare plugin
First you need to install Vagrant VMware Utility
Then you can install the plugin
vagrant plugin install vagrant-vmware-desktop
I am using Ubuntu 20.04, and I am having the following error message on vagrant up
The executable 'bsdtar' Vagrant is trying to run was not
found in the PATH variable. This is an error. Please verify
this software is installed and on the path.
I tried:
sudo apt-get install libarchive-tools
but got the error:
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package libarchive-tools
I just setup a vagrant box with archlinux on ubuntu 20.04 and also got the same error. I was able to fix my issue by running
sudo apt install libarchive-tools
Maybe you need to run
sudo apt update
to update your apt database
I have created a new virtual instance of Ubuntu 18.10
On this fresh installation, I then installed Anaconda as per the installation instructions (using curl, which I also installed).
The next thing I did (quite literally) after verifying conda was correctly installed was to install xeus-cling via
conda install xeus-cling -c QuantStack -c conda-forge
After downloading all the packages, the install fails with this error:
Executing transaction: failed ERROR conda.core.link:_execute(502): An
error occurred while installing package 'QuantStack::gcc-7-7.2.0-2'.
LinkError: post-link script failed for package
QuantStack::gcc-7-7.2.0-2 running your command again with -v will
provide additional information location of failed script:
/home/anaconda/anaconda3/bin/.gcc-7-post-link.sh
==> script messages <==
Attempting to roll back.
Rolling back transaction: done
LinkError: post-link script failed for package
QuantStack::gcc-7-7.2.0-2 running your command again with -v will
provide additional information location of failed script:
/home/anaconda/anaconda3/bin/.gcc-7-post-link.sh
==> script messages <==
I have repeated this several times, and the error is always the same. Any idea how to resolve the problem? It looks like an issue with the version of gcc, but I'm not sure how to resolve/fix it.
Other conda packages (i.e. SciJava) install without problems (tested in other instances of this process).
Ran into the same issue and resolved it by running
sudo apt-get update
sudo apt-get install -y build-essential
I ran into it on the anaconda3 docker image - so your mileage may vary.
I was trying to install ejabberd with applying the tutorials in many site to my VM which is ubuntu but I am stuck in the beginning. After I wrote
sudo apt-get update
sudo apt-get -y install ejabberd
it installs ejabberd. But when I try to write the following
ejabberdctl register admin localhost mypassword
it says ejabberdctl not found. I also tried to restart it with but it is still same.
sudo service ejabberd restart
Note: I did not install erlang seperately. Can it be the problem?
Try sudo ejabberdctl,
if it didn't work, Do:
sudo updatedb
sudo locate ejabberdctl
check if the output is in your $PATH variable.
I am trying to run a Vagrant box with SQL Server for local development. I am running Fedora 23. The box in question is this.
vagrant up fails with the following error message:
/usr/share/vagrant/plugins/communicators/winrm/shell.rb:9:in `require':
cannot load such file -- winrm (LoadError)
I have tried to install winrm with gem install winrm, and it installs just fine, but vagrant still fails.
The following ruby script runs without errors:
require "winrm"
puts "hello world"
Does anyone know how to fix this?
The winrm and winrm-fs gems are not packaged with Fedora or Debian. You can run:
$ vagrant plugin install winrm
$ vagrant plugin install winrm-fs
(i.e. vagrant plugin install, not gem install).
Note: Using Vagrant version 1.8.1, the winrm gem failed to install and this fixed it:
$ vagrant plugin install winrm --plugin-version 1.8.1
$ vagrant plugin install winrm-fs
Had the same issue:
With Ubuntu Ubuntu 20.04.1 LTS running ruby 2.7.0p0 and Vagrant 2.2.6
The solution that worked for me -
$ vagrant plugin install winrm
$ vagrant plugin install winrm-fs
$ vagrant plugin install winrm-elevated (this additional error showed after the first two were installed)
Not sure what the problem was, but I fixed it by uninstalling vagrant with dnf, and installing the latest version from vagrantup.com. Seems winrm is included in the latest vagrant version.
Same resolution as here: https://groups.google.com/forum/#!topic/vagrant-up/mBYMUHm-YBI
So this is an issue with the Debian packaged version of Vagrant. Installing the DEB package from https://www.vagrantup.com/downloads.html works (both for 1.6.5 and 1.7+).
780036 has been raised with Debian to track this issue.