Make it clear in the documentation that the full docker path needs to be specified, not the relative path

[kurniawano]

I tried to follow the steps in: https://jupyter.org/jupyter-book/guide/03_build

I created the book using:
$ jupyter-book create mybookname --demo

The building of the book was fine. But when I tried to run using docker, it gives me the following error:

$ docker run --rm --security-opt label:disable -v mybookname:/srv/jekyll -p 4000:4000 -it -u 1000:1000 emdupre/jupyter-book bundle exec jekyll server --host 0.0.0.0

Configuration file: none
            Source: /srv/jekyll
       Destination: /srv/jekyll/_site
 Incremental build: disabled. Enable with --incremental
      Generating...
       Jekyll Feed: Generating feed for posts
   GitHub Metadata: No GitHub API authentication could be found. Some fields may be missing or have incorrect data.
   GitHub Metadata: Error processing value 'title':
  Liquid Exception: No repo name found. Specify using PAGES_REPO_NWO environment variables, 'repository' in your configuration, or set up an 'origin' git remote pointing to your github.com repository. in feed.xml
             ERROR: YOUR SITE COULD NOT BE BUILT:
                    ------------------------------------
                    No repo name found. Specify using PAGES_REPO_NWO environment variables, 'repository' in your configuration, or set up an 'origin' git remote pointing to your github.com repository.

I am using MacOS X.

It seems it has something with github metadata. But I tried to build this locally. I attached the Gemfile and Gemfile.lock here.

Archive.zip

[emdupre]

Thanks for posting @kurniawano ! Could you confirm that the folder mybookname is in your current working directory ? We often see this error when the paths are don't match up. It might help to just provide the full absolute path, something like

docker run --rm --security-opt label:disable -v /full/path/to/mybookname:/srv/jekyll -p 4000:4000 -it -u 1000:1000 emdupre/jupyter-book bundle exec jekyll server --host 0.0.0.0

Could you try that and confirm you still see the same error ?

[choldgraf]

I think that @fperez ran into some issues getting the local Dockerfile build to work as well. @emdupre do you wanna do a debug session with me on the Dockerfile so we can try to pin down why some folks are running into issues?

[emdupre]

@emdupre do you wanna do a debug session with me on the Dockerfile so we can try to pin down why some folks are running into issues?

Yes, absolutely !

[kurniawano]

@emdupre It works when I give the full absolute path. Thanks!

[emdupre]

@choldgraf do you want me to keep this open until we look into @fperez 's problem ? Or should we open another issue ?

[choldgraf]

@emdupre perhaps we can change this issue into "make it clear in the documentation that the full path needs to be specified, not the relative path", and then we can create another issue to improve these instructions?

I'm starting to think we'd all save ourselves more time in the long run by just figuring out how to get the website built with Hugo instead of Jekyll, even though it'd be more work in the short-run :-P