AdGuard doesn't start after update

[worf-nm]

Problem/Motivation

After updating from 2.4.1 to 2.5.0 the add-on stopped working

Expected behavior

Update to be successful and add-on to start

Actual behavior

After the update the errors in the log were: [cont-init.d] 00-banner.sh: exited 0. [cont-init.d] 01-log-level.sh: executing... parse error: Invalid numeric literal at line 2, column 0 parse error: Invalid numeric literal at line 2, column 0 /var/run/s6/etc/cont-init.d/01-log-level.sh: line 41: log_level: unbound variable [cont-init.d] 01-log-level.sh: exited 1.

Steps to reproduce

Just pressed the "Update" button on the add-on's Info page.

I tried the following with no success:

• set explicitly the log_level option.
• reinstalled and attempted start of the clean add-on
• reinstalled and restored a snapshot from 2.4.1
• uninstalled and restored 2.4.1 from the snapshot

The "only" things that changed besides the add-on version are the versions of the supervisor (225 to 229) and home assistant itself (0.110 to 0.113.3) in order to cover the prerequisites of 2.5.0.

Proposed changes

N/A

Edit: I'm running Home Assistant in docker, on UnRAID 6.8.3 Edit 2: The same thing happens with MariaDB and Bookstack plugins. Not sure if the issue is for here then.

[addons-assistant[bot]]

:wave: Thanks for opening your first issue here! If you're reporting a :bug: bug, please make sure you include steps to reproduce it. Also, logs, error messages and information about your hardware might be useful.

[worf-nm]

I reinstalled everything under a VM