S1nglebarrel

That is my thinking as well. I just ended up reading the other post where someone just put in a script that runs every day to clear out the /run. I ran it and it did do its job so fingers crossed this "Band-Aid" works.

Just chiming in that I to have this issue. It's weird though that /run is filling up now when I have been running the same amount of docker containers for over year.

I believe I am having the same issue. I notice now that the GPU stat doesn't show Plex utilizing the encoding/decoding process. Nothing else changed with the system outside of the latest OS updates. Is there a way to validate if HW decoding is being still be used?

@kutzilla When building the container I see their is an option to mount the config to a share/volume. When I put in for instance host Path: /user/appdata/unbound which maps to Container Path: /opt/unbound/etc/unbound/. I see some of the files/directories. However I'm unable to edit them unless I go in to the terminal and change the permissions. Even after doing that the container will not start and throws a critical error listed below. Any thoughts on how to resolve this? I'm hoping that it should be straight forward having share access to the unbound config files to modify them. [1634322343] unbound[1:0] fatal error: Could not read config file: /opt/unbound/etc/unbound/unbound.conf. Maybe try unbound -dd, it stays on the commandline to see more errors, or unbound-checkconf