windows: fork() function is unimplemented #16
Comments
|
Hi there! 👋 Thanks for stopping by. Ooo a windows user! 🗻 I haven't tested this on windows just yet - I can tell you for one that the host visibility part won't work out of the box. And looking at that output - seems like the daemon is having some trouble starting too. Let me spin up a windows VM and see if I can debug this. - Thanks for the report! 📋 |
|
Cool, thanks. I'm only a ruby beginner but will be glad to do what ever testing or confirming you might need from my end. |
ghost
assigned 
|
+1 |
|
+2, we just encountered the exact same error when using landrush plugin on a windows 7 64 bit machine. Any known workarounds or similar on this issue? |
|
Hey sorry about the issue! I'm still working on getting a Windows machine to test this on. If you can get me the output of the command with VAGRANT_LOG=debug that will help me narrow things down in the meantime.
|
|
I'll see what i can do. |
|
@O5ten ordered me to send you this. Here you have the log you asked for @phinze |
|
Any progress on this @phinze ? |
|
+1, is this going to be released any time soon? |
|
Hey folks, Sorry for the lack of progress on Windows support. I'm still without a Windows machine to test on. It's sort of a core problem in the library we use: Looks like I might be able to boot a Windows Server machine on Azure - I might try and investigate that to see if I can get vagrant up and running out in the cloud. ☁️ Anybody with a windows dev environment and some knowledge is welcome to chime in here though! 😀 |
phinze
changed the title
|
Yo @phinze you can use /~https://github.com/joefitzgerald/packer-windows to build yourself a windows vmware/vbox machine for vagrant. It will automatically download, configure, install using an evaluation edition. Boop boop, done 🚀 |
|
+1 To subscribe and also offer to be a tester on Windows 8. |
|
I can test on win7 64bit |
|
Same error here Windows 7 64bit. Any suggestion to fix? I know some Ruby but new with Vagrant. |
|
+1 - WIndows 8.1 here |
|
Thanks to @ghuntley I did get a windows dev environment up and running recently! I'll see if I can poke at landrush on windows this weekend. 💃 |
|
👯 |
|
any luck on this? same problem |
|
+1 WIndows 7 64bit |
|
I was having this error on Windows 8.1 as well with landrush. I don't think fork() is implemented on windows at all so need a windows specific way to spawn the background process. As an alternate fix recommended here for another issue you can install cygwin which is POSIX complaint and has fork() but vagrant has an embedded ruby that seems pretty hardwired so I couldn't get it to work reliably. |
|
// , I've run into a similar issue. I got the following chain of errors: |
|
I Just ran into the same issue on Windows 7 when trying to push my vagrant box to atlas : hp (master *) Modern_Ops $ vagrant push |
|
+1 Any progress on this I am getting same error on windows 7, works fine on my Mac but when trying to setup development environment for other developers I am at a stand still with this error, any help appreciated. |
|
Sadly, same problem here |
|
+1 |
|
I got this error and it went away when I uninstalled the vagrant-dns plugin. |
- Replacing use of Rexec with ChildProcess to avoid the use of fork() on Windows - Bumping the plugin version
- Replacing use of Rexec with ChildProcess to avoid the use of fork() on Windows - Bumping the plugin version
… chages in latest version and applying simple style fixes
- Replacing use of Rexec with plain Process#spawn calls - Downgrading rubydns gem to 0.8.5 to use EventMachine instead of Celluloid IO which won't run on Windows - Updating command.rb to no rely on Rexec - Using printf in favor of /usr/bin/pr in order to format output in command.rb - Adding os.rb to allow for OS check
… chages in latest version and applying simple style fixes
- Replacing use of Rexec with plain Process#spawn calls - Downgrading rubydns gem to 0.8.5 to use EventMachine instead of Celluloid IO which won't run on Windows - Updating command.rb to no rely on Rexec - Using printf in favor of /usr/bin/pr in order to format output in command.rb - Adding os.rb to allow for OS check
… chages in latest version and applying simple style fixes
|
Resolved. |
|
Awesome work resolving this! When's the release including this due to go out? |
and others
First time using this and not sure if I'm even using it right :-)
Here is my vagrant file
This is the output
On Windows 7 pro 64bit but running 32bit vagrant and virtualbox
ruby 1.9.3
The text was updated successfully, but these errors were encountered: