Thank you. Maybe it is a Docker-specific bug and has nothing to do with the distribution itself? The problem occurred in both cases in Docker containers. I have added this in the bugtracker.