# Command, "vagrant up" in WSL is failed **URL:** https://discourse.roots.io/t/command-vagrant-up-in-wsl-is-failed/16528 **Category:** trellis **Tags:** trellis **Created:** 2019-09-05T08:44:29Z **Posts:** 4 **Showing post:** 2 of 4 ## Post 2 by @connerbw — 2019-09-05T13:03:22Z See [this (closed) issue](https://github.com/roots/trellis/issues/1083). Short version: [Roots doc say](https://roots.io/getting-started/docs/windows-development-environment-trellis/): alias `vagrant` in WSL to `vagrant.exe` [Vagrant docs say](https://www.vagrantup.com/docs/other/wsl.html): Vagrant _must_ be installed within the Linux distribution used with WSL. While the `vagrant.exe` executable provided by the Vagrant Windows installation is accessible from within the WSL, it will not function as expected. If you follow the _Vagrant docs_, the “Cannot translate name. @ rb\_sysopen” goes away. That being said, I couldn’t get it working under WSL. [Many](https://discourse.roots.io/t/vagrant-up-base-error-win10/15365) [other](https://discourse.roots.io/t/error-when-deploying-playbookcli-object-has-no-attribute-options/15618) [problems](https://discourse.roots.io/t/vagrant-up-wont-work-netsh-and-cscript-error/10111) [happened](https://github.com/Microsoft/WSL/issues/1426). If you checkout the latest commits from the github master branch, and install from DOS as admin, It works. Specifically, this commit: > --- _[View the full topic](https://discourse.roots.io/t/command-vagrant-up-in-wsl-is-failed/16528)._