anyproto / anyproto/any-sync-dockercompose

Instructions to run in rootless containers

Open
#151 13 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Shell
Stars
941
Forks
134
Avg merge
2d 21h
Merged PRs (30d)
3

Description

Have you read a contributing guide?
  • I have read CONTRIBUTING.md
  • I have searched the existing requests and didn't find any that were similar
  • I have considered creating a pull request instead and want to proceed
Clear and concise description of the problem

Currently, the containers run as root, meaning that all files and folders created belong to root, resulting in troubles when trying to back up the storage folder (as well as eventual security concerns linked to running containers as root in general).

Suggested solution

It would be nice to add in the doc instructions on how to run anytype without root privileges, like using UID/GID=1000/1000. And it might be even better to be the default if possible (I'm not sure if you need root for some features?)

Alternative

Currently, to back up the storage directory, you need either to run your backup utility as root, or chown the whole directory to your user. Both solutions are not ideal.

Additional context

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with CONTRIBUTING.md and the repository’s existing Docker Compose instructions, then trace how the storage folder and UID/GID settings are configured. Document a rootless-container setup using UID/GID 1000/1000, including any limitations found; done means a user can follow the instructions without root-owned storage files.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker-compose, shell
Domain
devops, documentation
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.