jekyll serve not working on Windows Subsystem for Linux #5233

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

Projects

None yet

4 participants

@TAGraves
  • 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/BashOnWindows#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
Member

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.)

@envygeeks envygeeks self-assigned this Aug 11, 2016
@envygeeks envygeeks added this to the 3.2.2 milestone Aug 11, 2016
@TAGraves

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

@envygeeks envygeeks added a commit that referenced this issue Aug 12, 2016
@envygeeks envygeeks Fix #5233: Increase our ability to detect Windows.
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
1658dc3
@envygeeks envygeeks referenced this issue in Microsoft/BashOnWindows Aug 12, 2016
Closed

Filesystem watchers like libinotify do not work #216

@envygeeks envygeeks added a commit that referenced this issue Aug 12, 2016
@envygeeks envygeeks Fix #5233: Increase our ability to detect Windows.
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
eb5301b
@envygeeks envygeeks added a commit that referenced this issue Aug 12, 2016
@envygeeks envygeeks Fix #5233: Increase our ability to detect Windows.
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
03f5288
@envygeeks envygeeks added a commit that referenced this issue Aug 12, 2016
@envygeeks envygeeks Fix #5233: Increase our ability to detect Windows.
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
74c52fc
@envygeeks envygeeks added a commit that referenced this issue Aug 12, 2016
@envygeeks envygeeks Fix #5233: Increase our ability to detect Windows.
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
fbae5a6
@envygeeks envygeeks added a commit that referenced this issue Aug 16, 2016
@envygeeks envygeeks Fix #5233: Increase our ability to detect Windows.
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
6e83a2b
@envygeeks envygeeks added a commit that referenced this issue Aug 16, 2016
@envygeeks envygeeks Fix #5233: Increase our ability to detect Windows.
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
6dcbc6a
@cnryb
cnryb commented Sep 3, 2016

@envygeeks Thank you! I got the same question。

@jekyllbot jekyllbot pushed a commit that closed this issue Sep 7, 2016
@envygeeks envygeeks Fix #5233: Increase our ability to detect Windows.
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
f1f8319
@jekyllbot jekyllbot closed this in f1f8319 Sep 7, 2016
@parkr parkr modified the milestone: 3.2.2, 3.3 Sep 20, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment