Ensure write permissions in nextdata volume root #116
Open
opened 2026-08-18 12:52:34 +00:00 by simon
·
2 comments
No Branch/Tag Specified
main
renovate/redis-8.x
renovate/docker.elastic.co-elasticsearch-elasticsearch-9.x
renovate/nginx-1.x
update_33.0.8
renovate/pgautoupgrade-pgautoupgrade-18.x
pr-15.2.0+34.0.2-fpm
pr-14.1.0+33.0.7-fpm
pr-14.2.0+33-fpm
pr-15.1.0+34.0.2-fpm
pr-15.0.0+34.0.2-fpm
pr-14.0.1+33.0.7-fpm
feat/check-major-upgrade
pr-14.0.0+33-fpm
temp
fix/nginx-conf-config-name
pr-13.2.0+32-fpm
upload-limit
feature/imaginary
kc_stable
nextcloud-v28
add-theming-v28.0.5
add-theming
update-nginx-conf
split-bbb-onlyoffice-compos
split-onlyoffice-bbb-config
authentik_sso
healthchecks
occ_cmds
auto_app_install
embed_nextcloud_in_iframe
auto_configure_sso
add-postgres-db
14.1.1+33.0.8-fpm
14.1.0+33.0.7-fpm
14.0.1+33.0.7-fpm
14.0.0+33.0.7-fpm
13.2.0+32-fpm
13.1.5+32.0.13-fpm
13.1.4+32.0.13-fpm
13.1.3+32.0.13-fpm
13.1.2+32.0.13-fpm
13.1.1+32.0.12-fpm
13.1.0+32.0.11-fpm
13.0.1+32.0.3-fpm
13.0.0+32.0.3-fpm
12.1.0+31.0.6-fpm
12.0.1+31.0.6-fpm
12.0.0+31.0.6-fpm
11.4.0+30.0.6-fpm
11.4.0+30.0.10-fpm
11.3.0+30.0.6-fpm
11.2.0+30.0.6-fpm
11.1.0+30.0.6-fpm
11.0.1+30.0.4-fpm
11.0.0+30.0.4-fpm
10.0.0+30.0.4-fpm
9.2.0+29.0.8-fpm
6.0.11+28.0.10-fpm
6.0.10+28.0.10-fpm
6.0.9+28.0.10-fpm
9.1.2+29.0.5-fpm
6.0.8+28.0.5-fpm
6.0.7+28.0.5-fpm
9.1.0+29.0.5-fpm
9.0.0+29.0.5-fpm
6.0.6+28.0.5-fpm
8.0.1+29.0.3-fpm
8.0.0+29.0.1-fpm
7.0.3+29.0.1-fpm
6.0.5+28.0.5-fpm
7.0.2+29.0.1-fpm
7.0.1+29.0.1-fpm
7.0.0+29.0.0-fpm
6.0.4+28.0.5-fpm
6.0.3+28.0.5-fpm
6.0.2+28.0.5-fpm
5.0.3+27.0.1-fpm
6.0.1+28.0.2-fpm
6.0.0+28.0.1-fpm
5.2.0+27.1.5-fpm
5.1.1+27.1.5-fpm
5.1.0+27.1.3-fpm
5.0.2+27.0.1-fpm
5.0.1+27.0.1-fpm
5.0.0+27.0.0-fpm
4.0.7+26.0.2-fpm
4.0.6+26.0.2-fpm
4.0.5+26.0.2-fpm
4.0.4+26.0.2-fpm
4.0.3+26.0.2-fpm
4.0.2+26.0.2-fpm
4.0.1+26.0.1-fpm
4.0.0+26.0.1-fpm
3.3.2+25.0.6-fpm
3.3.1+25.0.5-fpm
3.3.0+25.0.5-fpm
3.2.0+25.0.4-fpm
3.1.2+25.0.4-fpm
3.1.1+25.0.1-fpm
3.1.0+25.0.1-fpm
3.0.1+25.0.1-fpm
3.0.0+25.0.1-fpm
2.1.4+24.0.6-fpm
2.1.3+24.0.5-fpm
2.1.2+24.0.3-fpm
2.1.1+24.0.2-fpm
2.1.0+24.0.0-fpm
2.0.0+23.0.4-fpm
1.0.0+23.0.1-fpm
No labels
Milestone
No items
No Milestone
Assignees
3wordchant
aadil (Aadil Ayub)
abra-bot (Abra Bot)
ammaratef45
amras (Sarma)
BornDeleuze
Brooke
cas (Cassowary)
coopcloud
dannygroenewegen (Danny Groenewegen)
decentral1se (d1)
fauno (fauno)
ineiti (Linus Gasser)
javielico (Javielico)
jjsfunhouse
kawaiipunk (KawaiiPunk)
knoflook
moosemower
notplants
oxaliq (sorrel)
p4u1
renovate-bot (Comrade Renovate Bot)
stevensting
trav (Trav Fryer)
yksflip
Clear assignees
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: coop-cloud/nextcloud#116
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
We had issues with Nextcloud when restarting our VMs where the permissions on the root path of the nextdata volume got changed to the root user.
While the core issue probably lays in our system update routine, ensuring the correct access to the root directory (not recursively) would make the app itself more resilient against this.
Example solution in wordpress:
Proposal to add:
Looks safe to add this. Was it only the nextdata that was changed? Or also other volumes where maybe it did not directly cause an issue?
was only nextdata