Drop paragarph about anonymous (unnamed) volumes under Persistent Storage section fo the docs
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 72/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Stale
- Tech stack
- docker
- Domain
- documentation
Research direction
Open the README's Persistent Storage section and review the two opening paragraphs about unnamed and named Docker volumes. Remove the misleading anonymous-volume paragraph as proposed, keep the supported named-volume or host-directory guidance clear, and verify the surrounding section still explains the database and Nextcloud storage requirements.
Written by the indexing model from the issue text.
Description
The opening paragraphs for Persistent Storage in the README are somewhat misleading unless you already know what anonymous (unnamed) volumes are and their implications. It almost sounds like you don't need to do have a named volume at all, but then the next paragraph goes on to suggest otherwise without further context. We can probably tighten this section up a bit.
Current:
The Nextcloud installation and all data beyond what lives in the database (file uploads, etc.) are stored in the unnamed docker volume volume /var/www/html. The docker daemon will store that data within the docker directory /var/lib/docker/volumes/.... That means your data is saved even if the container crashes, is stopped or deleted.
A named Docker volume or a mounted host directory should be used for upgrades and backups. To achieve this, you need one volume for your database container and one for Nextcloud.
Currently I'm leaning towards dropping the first paragraph entirely, since it's more a behind-the-scenes implementation detail and not one particularly relevant to admins. There aren't any realistic scenarios where relying on the anonymous volume is a valid/supported configuration (outside the lab maybe) that I can think of.
- Dominant language
- Shell
- Stars
- 7.4k
- Forks
- 1.9k
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from nextcloud/docker
-
1. To develop bug feature: cron image
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
0. Needs triage bug
Difficulty 3/5 1-2 days Newbie friendliness 64/100
-
0. Needs triage bug
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Imagick architecture mismatch (x86_64 vs aarch64) on official arm64 image causes Apache segfaults Open0. Needs triage bug
Difficulty 4/5 3-5 days Newbie friendliness 50/100
All issues in nextcloud/docker
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
danielmiessler/LifeOS#2218 ·
-
docs(agents): strengthen the no-backslash-escaped-backticks rule with an issue-creation example Open
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
package-update
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
oSoWoSo/vOid_Community_repOsitory#148 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
chore
Difficulty 1/5 Under an hour Newbie friendliness 91/100
alunduil/alunduil-chezmoi#792 ·