Setting LOG_LEVEL to "WARNING" spams the logs with "sh: out of range"

Summary

I tried setting the log level to "WARNING", but now the warning (?) "sh: out of range" is spammed multiple times, which is not the case when you set the log level to INFO or ERROR.

Expected Behavior

Log level INFO:

2024-10-03 10:22:02 - INFO - Container started
2024-10-03 10:22:02 - INFO - Running vaultwarden-backup version latest@2024-10-01T02:01:09+00:00
2024-10-03 10:22:02 - INFO - Log level set to INFO
2024-10-03 10:22:02 - INFO - Running in manual mode.
2024-10-03 10:22:03 - INFO - Successfully created backup /myBackup/2024-10-03-102202_backup.tar.xz

Log level WARNING: ** No output or at least the output from WARNING should be included in INFO too **

Log level ERROR: No output

Current Behavior

Log level INFO:

2024-10-03 10:22:02 - INFO - Container started
2024-10-03 10:22:02 - INFO - Running vaultwarden-backup version latest@2024-10-01T02:01:09+00:00
2024-10-03 10:22:02 - INFO - Log level set to INFO
2024-10-03 10:22:02 - INFO - Running in manual mode.
2024-10-03 10:22:03 - INFO - Successfully created backup /myBackup/2024-10-03-102202_backup.tar.xz

Log level WARNING:

sh: out of range
sh: out of range
sh: out of range
sh: out of range
sh: out of range
sh: out of range
sh: out of range
sh: out of range
sh: out of range
sh: out of range
sh: out of range
sh: out of range
sh: out of range
sh: out of range
sh: out of range
sh: out of range
sh: out of range
sh: out of range
sh: out of range
sh: out of range
sh: out of range

Log level ERROR: No output

Possible Solution

Steps to reproduce

Execute: `docker run --rm --volumes-from=bitwarden -e UID=1100 -e GID=1100 -e BACKUP_DIR=/myBackup -e BACKUP_DIR_PERMISSIONS=770 -e LOG_LEVEL=ERROR -e TIMESTAMP=true -v ./backups:/myBackup bruceforce/vaultwarden-backup manual

Settings (Environment)

I think all the relevant environment variables are in the command above?