tg-spam.log permission denied #68
Replies: 2 comments 2 replies
-
This one has nothing to do with tg-spam but rather a way docker-compose handles direction creation if one of the mounted dirs is missing. In this case, it will make the directory under the root. You can chown/chmod it and restart it. Or even better - before you run compose for the first time, make sure this directory is created under your user |
Beta Was this translation helpful? Give feedback.
2 replies
-
I think when folder ./logs doesn't exist on the host, than docker create it with root permission, I changed owner on it, and it works now, thanks |
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
-
Hi umputun,
I used docker-compose to deploy the application, and I see a warning
in container I see created folders from root user:
/srv $ ls -la total 14356 drwxr-xr-x 1 root root 4096 Mar 24 11:07 . drwxr-xr-x 1 root root 4096 Mar 24 11:07 .. drwxrwxr-x 2 app app 4096 Mar 24 11:09 data drwxr-xr-x 2 root root 4096 Mar 24 11:07 logs -rwxr-xr-x 1 root root 14684160 Mar 24 07:22 tg-spam /srv $ ps -a PID USER TIME COMMAND 1 app 0:04 /srv/tg-spam 22 app 0:00 /bin/sh 30 app 0:00 ps -a
on host mashine folder ./logs created from root:
Beta Was this translation helpful? Give feedback.
All reactions