this post was submitted on 04 Apr 2026
9 points (90.9% liked)

Linux 101 stuff. Questions are encouraged, noobs are welcome!

1477 readers
1 users here now

Linux introductions, tips and tutorials. Questions are encouraged. Any distro, any platform! Explicitly noob-friendly.

founded 2 years ago
MODERATORS
 

There's a lot I don't understand about both docker and git, so my question and description of the problem may not be as detailed as some would like.

I've set up a container, Otter wiki, via the docker compose file offered in the docs. This sets up a persistent volume outside the container where the wiki config and git repo containing the wiki's pages live. Everything works fine. I can go to the site and everything works. But I want to add external files to the repo. When I try to do it, it throws an error saying I need to enter my email and user name. I do this, and it still says permission denied.

I assume the instance of git that's tracking the repo lives inside the docker container, but the repo itself lives outside the container. How do I add and commit files?

CLARIFYING EDIT:

The repo I'm trying to use isn't for Otter's source code. Otter uses git as the revision tracking system component common to most wikis. That is, the wiki itself is a git repo filled with markdown files. In order to add a bunch of existing markdown files to the wiki, I have to tell git to track them, but this is a persistent volume outside the container, so the instance of git I'm using is on the host, but the instance of git that's tracking the files is in the container.

you are viewing a single comment's thread
view the rest of the comments
[โ€“] early_riser@lemmy.world 1 points 3 days ago (1 children)

Thanks. I had been skipping over the git-specific portions of the docs because it didn't click that it would be relevant. It sounds like the intended way to add files is to add the files to a local repo, then push them to the wiki. I still have to figure out how that works but you've pointed me in the right direction for further troubleshooting.

[โ€“] folekaule@lemmy.world 1 points 3 days ago

Happy to help. You may want to check out the section on Repository Management.

The key here is to just treat it like any other git repo (like one on GitHub). In fact, you can set it up to pull/push from/to GitHub or another repo also, for off-site backup or collaboration outside your network.

Make sure to clone the report to a local working copy first. From there, it should be pretty simple once you're familiar with the most common git commands (or use a UI).