Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

jekyll serve not working on Windows Subsystem for Linux #5233

Closed
TAGraves opened this issue Aug 11, 2016 · 3 comments
Closed

jekyll serve not working on Windows Subsystem for Linux #5233

TAGraves opened this issue Aug 11, 2016 · 3 comments

Comments

@TAGraves
Copy link

@TAGraves TAGraves commented Aug 11, 2016

  • I believe this to be a bug, not a question about using Jekyll.
  • I Updated to the latest Jekyll (or) if on Github Pages to the latest github-pages
  • I Read the CONTRIBUTION file at https://jekyllrb.com/docs/contributing/

  • I am on (or have tested on) _Windows_ 10+

  • It was another bug.

My Reproduction Steps

jekyll serve
Configuration file: /path/to/_config.yml
            Source: /path/to
       Destination: /path/to/_site
 Incremental build: disabled. Enable with --incremental
      Generating...
                    done in 0.062 seconds.
jekyll 3.1.6 | Error:  Invalid argument - Failed to watch "/path/to/.git/hooks": the given event mask contains no legal events; or fd is not an inotify file descriptor.

This is almost certainly due to microsoft/WSL#216. I'm not sure if there's any viable workaround at the moment, but figured (1) it was worth bringing this to the jekyll team's attention, and (2) having a public issue for other users who run into this problem.

@envygeeks
Copy link
Contributor

@envygeeks envygeeks commented Aug 11, 2016

I'll get on my Windows system tonight to determine if we can reliably detect Windows+Bash Subsystem, I don't know if we can because last I remember the system information thought it was Linux but there must be a way. I can always push something up to Jekyll-Watch that detects the lack of /proc/fs structure and retreats to polling instead.

That said, you should in theory be able to poll. Try running your command again with "--force-polling" and see what happens (you might have to do "--force_polling" I don't remember if the CLI treats them the same.)

@TAGraves
Copy link
Author

@TAGraves TAGraves commented Aug 11, 2016

Thanks for the response! --force_polling does indeed work.

envygeeks added a commit that referenced this issue Aug 12, 2016
Jordon Bedwell
This increases our ability to detect Windows, and to detect Windows+Bash.  It also adds a message to Windows for users who try to "--watch", also noting to to them to check out the Windows ticket so eventually somebody pings us if this issue is fixed. /cc @TAGraves
envygeeks added a commit that referenced this issue Aug 12, 2016
Jordon Bedwell
This increases our ability to detect Windows, and to detect Windows+Bash.  It also adds a message to Windows for users who try to "--watch", also noting to to them to check out the Windows ticket so eventually somebody pings us if this issue is fixed. /cc @TAGraves
envygeeks added a commit that referenced this issue Aug 12, 2016
Jordon Bedwell
This increases our ability to detect Windows, and to detect Windows+Bash.  It also adds a message to Windows for users who try to "--watch", also noting to to them to check out the Windows ticket so eventually somebody pings us if this issue is fixed. /cc @TAGraves
envygeeks added a commit that referenced this issue Aug 12, 2016
Jordon Bedwell
This increases our ability to detect Windows, and to detect Windows+Bash.  It also adds a message to Windows for users who try to "--watch", also noting to to them to check out the Windows ticket so eventually somebody pings us if this issue is fixed. /cc @TAGraves
envygeeks added a commit that referenced this issue Aug 12, 2016
Jordon Bedwell
This increases our ability to detect Windows, and to detect Windows+Bash.  It also adds a message to Windows for users who try to "--watch", also noting to to them to check out the Windows ticket so eventually somebody pings us if this issue is fixed. /cc @TAGraves
envygeeks added a commit that referenced this issue Aug 16, 2016
Jordon Bedwell
This increases our ability to detect Windows, and to detect Windows+Bash.  It also adds a message to Windows for users who try to "--watch", also noting to to them to check out the Windows ticket so eventually somebody pings us if this issue is fixed. /cc @TAGraves
envygeeks added a commit that referenced this issue Aug 16, 2016
Jordon Bedwell
This increases our ability to detect Windows, and to detect Windows+Bash.  It also adds a message to Windows for users who try to "--watch", also noting to to them to check out the Windows ticket so eventually somebody pings us if this issue is fixed. /cc @TAGraves
@cnryb
Copy link

@cnryb cnryb commented Sep 3, 2016

@envygeeks Thank you! I got the same question。

@jekyllbot jekyllbot closed this in f1f8319 Sep 7, 2016
@parkr parkr modified the milestones: 3.2.2, 3.3 Sep 20, 2016
@jekyll jekyll locked and limited conversation to collaborators Jul 11, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
5 participants
You can’t perform that action at this time.