Description

When v14 introduced a change to skip most of the container startup scripts when the container is detected as restarted instead of a fresh instance, this also excluded ownership corrections.

A user report notes that when their Docker host is restarted, that ownership is being adjusted externally from DMS, and when the container implicitly starts again (effectively a container restart), this leads to incorrect ownership.

Technically this is an issue on their end, but the intent of skipping scripts for DMS container restarts should continue to avoid regressions if we allow ownership fixes to run.