Then, I ran vagrant init, edited the vagrantfile to be like this one here, except with zesty rather than trusty, then ran vagrant up. I manually deleted the folders in the files app: VirtualBox VMs. Press Check to open the Virtual Media Manager window and see which files are inaccessible, or press Ignore to ignore this message. As a result, you will not be able to operate virtual machines that use these files until they become accessible later. ![]() One or more disk image files are not currently accessible. When I opened Virtual Box I got the error message: There was an error while executing `VBoxManage`, a CLI used by Vagrant for controlling VirtualBox. => default: Running 'pre-boot' VM customizations. => default: Preparing network interfaces based on configuration.ĭefault: 22 (guest) => 2222 (host) (adapter 1) => default: Clearing any previously set network interfaces. => default: Clearing any previously set forwarded ports. => default: Checking if box 'ubuntu/zesty64' is up to date. => default: Attempting graceful shutdown of VM. I considered deleting /usr/lib/node_modules and running vagrant provision again, but I haven't yet. VagrantĪssumes that this means the command failed. The SSH command responded with a non-zero exit status. => default: cannot move 'node-v8.3.0-linux-圆4/lib/node_modules' to '/usr/lib/node_modules' Then finally the output ended with: => default: mv:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |