Created at 2020-07-02 01:04:18 by firstyear (@Firstyear)
Assigned to nobody
Issue Description
A early adopter of the 389 container noticed that if you bind mount in schema, this causes first run to fail as the "directory already exists". We should probably be more careful about this scenario in our dscontainer script and allow some locaitons to "already exist" if they are known config injection points.
Cloned from Pagure issue: https://pagure.io/389-ds-base/issue/51200
Issue Description
A early adopter of the 389 container noticed that if you bind mount in schema, this causes first run to fail as the "directory already exists". We should probably be more careful about this scenario in our dscontainer script and allow some locaitons to "already exist" if they are known config injection points.