@celeste_42bit
Afraid not, no. But I do know that the user account used by the Docker container almost certainly doesn't match up with an account on the host. Worse, the default behaviour is to store that directory on the host rather than in the container.

Thus the permissions of that directory are usually weird, owned by uid 991 (IIRC). If that isn't true, the directory probably appears read-only from within the container. Or if Docker isn't told to map the host directory inside the container, that directory won't exist within the container. Both situations could explain what you're seeing.