Describe the bug
Docker entrypoint script try to chown '.' if log path is not set in config because LOG_DIR = $(dirname "" || true) returns '.'

Does it reproduce on recent release?
21.3.3.14

How to reproduce
Remove logger.log or logger.errorlog from config.xml.

Expected behavior
The docker container should start without trying to chown '.', which resolves to / since the entrypoint script is located at /.

Error message and/or stacktrace
Poco::Exception. Code: 1000, e.code() = 0, e.displayText() = Not found: logger.log (version 21.3.3.14 (official build))
Poco::Exception. Code: 1000, e.code() = 0, e.displayText() = Not found: logger.errorlog (version 21.3.3.14 (official build))
chown: changing ownership of './proc/fs/xfs/xqm': Read-only file system
chown: changing ownership of './proc/fs/xfs/stat': Read-only file system
chown: changing ownership of './proc/fs/xfs/xqmstat': Read-only file system
chown: changing ownership of './proc/fs/xfs': Read-only file system
chown: changing ownership of './proc/fs/cifs/Stats': Read-only file system
chown: changing ownership of './proc/fs/cifs/cifsFYI': Read-only file system

Additional context
I believe this bug was introduced by #18954 where the $LOG_PATH is surrounded with double quotes ("").