You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I delete both of the log directories on the host, the one for MariaDB gets created, and the permissions are set to the mariadb user (999). Logs are written correctly. Redis does not create the directory, and even when I manually create it on the host and run chown -R 999:999 on it, Redis does not write logs there.
You can also pass Redis configuration parameters using the command line directly.
When I remove the bind mount and this directory becomes an internal directory of the container, logging to the specified file works correctly. Besides, I think an issue has surfaced here:
debian@vps-13995eb5:~$ docker exec -it redis touch /var/log/redis/test
touch: cannot touch '/var/log/redis/test': No such file or directory
I have two containers in my Docker Compose stack running with non-root user permissions: Redis and MariaDB.
I created similar Dockerfiles for both of them:
When I delete both of the log directories on the host, the one for MariaDB gets created, and the permissions are set to the mariadb user (999). Logs are written correctly. Redis does not create the directory, and even when I manually create it on the host and run
chown -R 999:999
on it, Redis does not write logs there.Any ideas on how to manually fix this issue, and ideally make the Redis container behave like the MariaDB container?
The text was updated successfully, but these errors were encountered: