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

Errors building HTML #152

Closed
Benfeitas opened this issue Mar 25, 2019 · 6 comments
Closed

Errors building HTML #152

Benfeitas opened this issue Mar 25, 2019 · 6 comments

Comments

@Benfeitas
Copy link

Benfeitas commented Mar 25, 2019

I'm following the guide in here. I have installed docker and I can build the jupyter book. However, when running

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

I get

Could not find public_suffix-2.0.5 in any of the sources
Run `bundle install` to install missing gems.

Running bundle install gives

Bundle complete! 8 Gemfile dependencies, 107 gems now installed.
Bundled gems are installed into `./vendor/bundle`

But I still get the public_suffix error above when I run the docker run ... line. Any suggestions on how to solve this? Thanks a lot in advance

@choldgraf
Copy link
Member

Hmmm - I'm not sure if this is a Docker-related bug, but if so I think that @emdupre might be able to help out!

@emdupre
Copy link
Collaborator

emdupre commented Mar 25, 2019

Sorry for the trouble, here ! Can you try deleting your Gemfile.lock or run jupyter book upgrade ?

@Benfeitas
Copy link
Author

Thanks so much @emdupre , deleting Gemfile.lock solved the issue :)

@mathieuboudreau
Copy link
Contributor

@emdupre seems like this problem/solution repeats itself quite a lot. Any workflow and/or documentation solution we could implement to highlight the importance of this step?

@choldgraf
Copy link
Member

I opened up #154 to chat about the gemfile lock bug specifically

@choldgraf
Copy link
Member

gonna close this one since I think we've got this issue resolved, and we now have another issue to specifically talk about the gemfile lock situation!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants