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

Opening che-doc repository in Che #16624

Closed
petzsch opened this issue Apr 16, 2020 · 2 comments
Closed

Opening che-doc repository in Che #16624

petzsch opened this issue Apr 16, 2020 · 2 comments
Labels
area/doc Issues related to documentation kind/bug Outline of a bug - must adhere to the bug report template. severity/P1 Has a major impact to usage or development of the system.

Comments

@petzsch
Copy link

petzsch commented Apr 16, 2020

Summary

When trying to open the che-doc repository with the devfile provided by the project + adding the git repository to it, I don't get a workspace that I can run the jekyll serve command in.

Relevant information

It seems that the CMD line of the image quay.io/eclipse/che-docs:latest automatically starts jekyll in a path /che-docs/ which is not where Che normally locates the projects. Hence, when I open the webbrowser on that container, I get an empty directory listing.

I would propose to change the CMD line in the Dockerfile to:
CMD ["tail", "-f", "/dev/null"]

And let the IDE handle the starting of jekyll within the correct workingdir.

@petzsch petzsch added the kind/question Questions that haven't been identified as being feature requests or bugs. label Apr 16, 2020
@che-bot che-bot added the status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. label Apr 16, 2020
@amisevsk
Copy link
Contributor

I can reproduce various issues on che.openshift.io (using the factory URL: https://che.openshift.io/f?url=https://github.com/eclipse/che-docs):

  • che-docs-livereload-server endpoint does not work, showing only the plaintext message This port only serves livereload.js over HTTP. (endpoints are all https, as of
  • che-docs-web-server shows an "index of /" page.
  • serve che-docs command fails with
     #<Thread:0x000055d9a9ce4f90@/usr/local/bundle/gems/jekyll-3.8.5/lib/jekyll/commands/serve/live_reload_reactor.rb:41 run> terminated with exception (report_on_exception is true):
     Traceback (most recent call last):
     	5: from /usr/local/bundle/gems/jekyll-3.8.5/lib/jekyll/commands/serve/live_reload_reactor.rb:44:in `block in start'
     	4: from /usr/local/bundle/gems/eventmachine-1.2.7/lib/eventmachine.rb:195:in `run'
     	3: from /usr/local/bundle/gems/eventmachine-1.2.7/lib/eventmachine.rb:195:in `run_machine'
     	2: from /usr/local/bundle/gems/jekyll-3.8.5/lib/jekyll/commands/serve/live_reload_reactor.rb:47:in `block (2 levels) in start'
     	1: from /usr/local/bundle/gems/eventmachine-1.2.7/lib/eventmachine.rb:531:in `start_server'
     /usr/local/bundle/gems/eventmachine-1.2.7/lib/eventmachine.rb:531:in `start_tcp_server': no acceptor (port is in use or requires root privileges) (RuntimeError)
     jekyll 3.8.5 | Error:  no acceptor (port is in use or requires root privileges)
    

I tried changing the command (by adding to the devfile) as suggested but it did not resolve the problem in my case

@sleshchenko sleshchenko added area/doc Issues related to documentation kind/bug Outline of a bug - must adhere to the bug report template. severity/P1 Has a major impact to usage or development of the system. and removed kind/question Questions that haven't been identified as being feature requests or bugs. status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. labels Apr 17, 2020
@themr0c
Copy link
Contributor

themr0c commented Jul 15, 2020

This is fixed now.

@themr0c themr0c closed this as completed Jul 15, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/doc Issues related to documentation kind/bug Outline of a bug - must adhere to the bug report template. severity/P1 Has a major impact to usage or development of the system.
Projects
None yet
Development

No branches or pull requests

5 participants