Replies: 2 comments
-
If I do a chmod 777 on the folder userfiles on the host it works. But this should not the proper way. Does anyone knows how the user is called which tries to write files from docker to that folder? |
Beta Was this translation helpful? Give feedback.
0 replies
-
I finally found the solution. You need to adjust the user inside the docker-container as follows:
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I have setup a docker container like in the example, the only difference is the bind mount of the volume, for persistent reasons even if docker breaks. Everything works fine despite that I am not able to upload anything.
Its turning forever.
My docker-compose.yml file looks like the following:
version: '3.3'
services:
leantime_db:
image: mysql:8.0
container_name: mysql_leantime
volumes:
- ./db_data:/var/lib/mysql
restart: always
env_file: ./.env # Environment file with settings
networks:
- leantime-net
command: --character-set-server=UTF8MB4 --collation-server=UTF8MB4_unicode_ci
leantime:
image: leantime/leantime:2.4.7
container_name: leantime
restart: always
env_file: ./.env # Environment file with settings
networks:
- leantime-net
volumes:
- ./public_userfiles:/var/www/html/public/userfiles # Volume to store public files, logo etc
- ./userfiles:/var/www/html/userfiles # Volume to store private user uploaded files
depends_on:
- leantime_db # Don't start Leantime unless leantime_db is running
networks:
leantime-net:
The magic is with the bind mount of the userfiles, as soon as I do - /userfiles:/var/www/html/userfiles it works.
Any suggestions?
Beta Was this translation helpful? Give feedback.
All reactions