Recently updated one of the hosts and the containers running on it from stretch to buster. With buster's 241-7~deb10u1 the issue still exists. I have tried working around this issue by setting a memory limit on the -.slice from within the container, but this is fairly unreliable.