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

[Self-Hosted RTD] Issue creating VENV #6893

Closed
Daltz333 opened this issue Apr 13, 2020 · 12 comments
Closed

[Self-Hosted RTD] Issue creating VENV #6893

Daltz333 opened this issue Apr 13, 2020 · 12 comments
Labels
Accepted Accepted issue on our roadmap Bug A bug Good First Issue Good for new contributors

Comments

@Daltz333
Copy link

Daltz333 commented Apr 13, 2020

I am aware that this is not a supported scenario, but any help is appreciated regardless.

My name is Dalton and currently developing a readthedocs docker image for streamlining self-hosting for the wpilibsuite organization. Following the installation steps through a standard ubuntu installation (on a separate machine running Ubuntu 18.04) seems to give a successful build, however my docker image seems to be failing with the below error message.

An additional note is if I log onto the docker image and run the command manually, it works just fine.

image

Attached is the full log from the docker output: https://hastebin.com/akahawusol.cs

Why are we self hosting? https://hastebin.com/upuxitited.coffeescript

@humitos
Copy link
Member

humitos commented Apr 13, 2020

Following the installation steps through a standard ubuntu

We moved away from that setup and we are using our own docker images now for development: https://docs.readthedocs.io/en/stable/development/standards.html

You may find some help from reading that guide and checking out how we create the Dockerfile's among others.

@humitos
Copy link
Member

humitos commented Apr 13, 2020

Why are we self hosting? https://hastebin.com/upuxitited.coffeescript

Reading those reasons, I wouldn't recommend follow this path. We can talk about giving more resources to your project (in fact, we have bigger builders now). I think you will have more problems by maintaining your own instance, but that's up to you, of course. My 2 cents.

@humitos humitos added the Support Support question label Apr 13, 2020
@humitos humitos added the Needed: more information A reply from issue author is required label Apr 21, 2020
@deepshikhagandhi
Copy link

deepshikhagandhi commented Apr 27, 2020

We have come across the same issue. Looks like there's an extra space introduced in that command due to d0ddcb6#diff-31f8391d8643c47c6caedf53930c0b7e

Reverting this back to site_packages = '--no-site-packages' fixes the problem.

@no-response
Copy link

no-response bot commented May 5, 2020

This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you have or find the answers we need so that we can investigate further. Thanks!

@no-response no-response bot closed this as completed May 5, 2020
@Daltz333
Copy link
Author

Daltz333 commented May 5, 2020

This issue is still present.

@no-response no-response bot removed the Needed: more information A reply from issue author is required label May 5, 2020
@no-response no-response bot reopened this May 5, 2020
@humitos
Copy link
Member

humitos commented May 5, 2020

Hi @Daltz333! Unfortunately, we do not offer support on custom installations. We have a note in our docs about this: https://docs.readthedocs.io/en/stable/open-source-philosophy.html#unsupported

@stsewd
Copy link
Member

stsewd commented May 5, 2020

This is because the version of virtualenv, in production we use https://github.com/readthedocs/readthedocs-docker-images/blob/f8db06c9cf64c3473a524c08b547805288b81f71/Dockerfile#L117

But in the repo we are pinning to

virtualenv==20.0.16

We should pin to the same version

@stsewd stsewd added Bug A bug Good First Issue Good for new contributors and removed Support Support question labels May 5, 2020
@stale
Copy link

stale bot commented Jun 20, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the Status: stale Issue will be considered inactive soon label Jun 20, 2020
@Daltz333
Copy link
Author

Not stale.

@stale stale bot removed the Status: stale Issue will be considered inactive soon label Jun 20, 2020
@stsewd stsewd added the Accepted Accepted issue on our roadmap label Jun 20, 2020
@DougCal
Copy link
Contributor

DougCal commented Jul 31, 2020

Since PR #7330 fixes issue #7322, is this one fixed as well? It was suggested that issue #7322 is the same as this one.

@stsewd
Copy link
Member

stsewd commented Jul 31, 2020

It should be fixed, but we still should use the same version as docker as outside docker.

@humitos
Copy link
Member

humitos commented Mar 18, 2021

I'm closing this issue since there is no action required from the core team. As I mentioned in my previous comment, unfortunately we do not offer support for self-hosted Read the Docs instances.

@humitos humitos closed this as completed Mar 18, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Accepted Accepted issue on our roadmap Bug A bug Good First Issue Good for new contributors
Projects
None yet
Development

No branches or pull requests

5 participants