Windows 10 Pro (20H2 update)
Ubuntu 18.04 LTS in WSL
I start the jekyll server inside bash. It serves up pages until the first time it detects the content has changed and it will do the rebuild. After that, replies on localhost:4000 stop. This happens if I start jekyll as
bundle exec jekyll serve or just
jekyll serve. It also happens if I start either of these commands in the background.
When I try to stop jekyll with ^C, I never get the prompt back. If I started the process in the background,
kill -9 <pid> doesn’t work either. The server still shows up with
ps -ef. Even more maddening, if I quit WSL, the process still lives in Windows space. I can see it in the Task Manager as
bash.exe. I can’t kill it from Task Manager, either, the process is grayed out. The only thing that will stop the process for me is a reboot.
I have a workaround where I
s3cmd sync the _site folder to an S3 bucket that I have set up as a staging site, but that’s a pain to do for hours on end.
I’ve used jekyll serve successfully in the past on a Mac and Linux without any problems. I’m assuming this is some oddity of using WSL, but I haven’t had this type of issue before. Ideas?