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

Permission error when hosting with official Docker image #2075

Open
ColdTeapot273K opened this issue Oct 4, 2024 · 1 comment
Open

Permission error when hosting with official Docker image #2075

ColdTeapot273K opened this issue Oct 4, 2024 · 1 comment

Comments

@ColdTeapot273K
Copy link

ColdTeapot273K commented Oct 4, 2024

Please read the CONTRIBUTION GUIDELINES before submitting!

If your have problems using or installing the software which stem from bugs in the software or a lack of documentation, we are always happy to help out! However, for ordinary usage questions, please consider asking elsewhere, for instance on StackOverflow.

Describe the bug
Gollum not functioning when deployed with Docker according to official manual.

To Reproduce
Steps to reproduce the behavior:

  1. Go to Docker guide
  2. Reproduce instruction steps.
  3. See error in browser:
Rugged::ConfigError at /
repository path '/wiki/' is not owned by current user

Expected behavior
Starting page.

For comparison, this community setup works. But it's not maintained and not updated.

P.S.
Docker Compose manual from here doesn't work either, with different kind of error about permissions when trying to save a document. Could you test it too please?

Environment Info
OS: Ubuntu 22.04.3 LTS x86_64
Docker version 25.0.1, build 29cf629

@marriotb
Copy link

I suspect that your first error ("Rugged::ConfigError") is related to the GitHub issue that's mentioned in the Docker Compose guide that you reference (step 4 in the instructions). Try adding the safe.directory value to your git config.

I, too, get the permissions error that you mention when following the Docker Compose guide. (Ubuntu 24.04.1 LTS on x86_64; Docker version 27.3.1; Docker Compose version v2.29.7) If I find a workaround, I'll post it here, otherwise I'll raise a separate issue.

Note that issue registers such as this should only reference one problem -- if there are two separate issues that have similar circumstances, raise them separately and cross-reference them. This ensures that each is addressed.

Regards
Brian

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

2 participants