[Bug]: Database volume is chowned to user 70 instead of root #544

Closed
opened 2026-02-04 20:18:43 +03:00 by OVERLORD · 1 comment
Owner

Originally created by @Nounoursdestavernes on GitHub (Jul 18, 2024).

Where is the problem occurring?

I encountered the problem while interacting with the server (Backend)

What browsers are you seeing the problem on?

No response

Current behaviour

Context :
I was trying to set up a backup solution for my self host planka.

Problem:
The volume that correspond to the db-data folder is chowned by planka to set the user to 70.

This manipulation prevent the readiness of the folder without either a chown either a sudo su -

Desired behaviour

The volume is not chowned by planka and stay as docker set it

Steps to reproduce

Launch the application through docker with volumes.

Other information

No response

Originally created by @Nounoursdestavernes on GitHub (Jul 18, 2024). ### Where is the problem occurring? I encountered the problem while interacting with the server (Backend) ### What browsers are you seeing the problem on? _No response_ ### Current behaviour Context : I was trying to set up a backup solution for my self host planka. Problem: The volume that correspond to the db-data folder is chowned by planka to set the user to 70. This manipulation prevent the readiness of the folder without either a chown either a sudo su - ### Desired behaviour The volume is not chowned by planka and stay as docker set it ### Steps to reproduce Launch the application through docker with volumes. ### Other information _No response_
Author
Owner

@Nounoursdestavernes commented on GitHub (Jul 31, 2024):

After some investigations this is due to the postgresql container. I close the issue

@Nounoursdestavernes commented on GitHub (Jul 31, 2024): After some investigations this is due to the postgresql container. I close the issue
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/planka#544