AGH suddenly stops functioning, unable to restart/stop the container.

[Welved]

Prerequisites

• I have checked the Wiki and Discussions and found no answer

• I have searched other issues and found no duplicates

• I want to report a bug and not ask a question or ask for help

• I have set up AdGuard Home correctly and configured clients to use it. (Use the Discussions for help with installing and configuring clients.)

Platform (OS and CPU architecture)

Linux, ARM64

Installation

Docker

Setup

On one machine

AdGuard Home version

Unable to check, container is stuck for some reason.

Action

Replace the following command with the one you're calling or a
description of the failing action:

nslookup -debug -type=a 'www.example.com' '$YOUR_AGH_ADDRESS'

Expected result

Have AGH function without any issues.

Actual result

At some point it ceases to function completely, but the container is still running. This issue is getting worse, at first it was a basic client block; now it is a straight up container fail.

No other container that have running exhibits the same issue/behavior that AGH is currently facing.

Additional information and/or screenshots

No response

[hvorragend]

It doesn't have to be related to this, but in v0.107.60 and v0.107.61 I have recently had the problem that the CPU processor load goes to 100% at around 6:30 am.
Only a restart helps here.

No Docker installation.
Runs under Proxmox LXC
Installation with the Proxmox Helper Scripts.