Folders of cloned repos owned by root #517

Closed
opened 2025-10-31 15:14:05 -05:00 by GiteaMirror · 1 comment
Owner

Originally created by @Morakanis on GitHub (Aug 15, 2025).

After troubleshooting for some hours I seem to have reached the dead end.

I deployed Komodo and the periphery via a compose file. Inside Komodo I added a repo of a local hosted gitlab instance. I was able to clone the repo onto my homeserver.

No to the problem:
When I edit the files in VS Code an try to save them, I get an error regarding permissions. Looking into that shows, that the created folders of the cloned repo are all owned by root and not the local user (named docker). Only root has write permissions for those files.
Of course I could manually change the permissions for all files but I would have to do that for every single repository I would clone in the future. Is this the way to do it or is there an underlying error/principle that I don´t see?

Originally created by @Morakanis on GitHub (Aug 15, 2025). After troubleshooting for some hours I seem to have reached the dead end. I deployed Komodo and the periphery via a compose file. Inside Komodo I added a repo of a local hosted gitlab instance. I was able to clone the repo onto my homeserver. No to the problem: When I edit the files in VS Code an try to save them, I get an error regarding permissions. Looking into that shows, that the created folders of the cloned repo are all owned by root and not the local user (named docker). Only root has write permissions for those files. Of course I could manually change the permissions for all files but I would have to do that for every single repository I would clone in the future. Is this the way to do it or is there an underlying error/principle that I don´t see?
Author
Owner

@mbecker20 commented on GitHub (Aug 19, 2025):

It clones it as whatever the user periphery runs as, in docker it will be root by default. You could probably get it working messing with the user running container in docker, or switch to systemd user install.

Personally I would treat these clones by periphery as deployed infrastructure and not edit them directly, but rather maintain separate clones on client devices, and allow Komodo to update the deployed repos after you push from elsewhere.

@mbecker20 commented on GitHub (Aug 19, 2025): It clones it as whatever the user periphery runs as, in docker it will be root by default. You could probably get it working messing with the user running container in docker, or switch to systemd user install. Personally I would treat these clones by periphery as deployed infrastructure and not edit them directly, but rather maintain separate clones on client devices, and allow Komodo to update the deployed repos after you push from elsewhere.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/komodo#517