When using directories, the docker images will start generaties files inside these directories, with root privileges.
These files cannot be removed by the user, even though he owned the directory.
So I decided to use volumes instead, since this alleviate the issue.
I'll add a volume management API letter. For the time being, you'll have to rely on docker-compose volume commands to manage them.
When using directories, the docker images will start generaties files inside these directories, with root privileges. These files cannot be removed by the user, even though he owned the directory.
So I decided to use volumes instead, since this alleviate the issue.
I'll add a volume management API letter. For the time being, you'll have to rely on docker-compose volume commands to manage them.
Signed-off-by: Myy Miouyouyou myy@miouyouyou.fr