Log shows errors that mount overlaps with non-empty folder

[navarr]

It's common that Magento installations have files in app/etc, pub/media, var/ and other writeable directories that are kept mounted. Platform.sh shows a warning when this happens, as these files would not ordinarily be available.

Magento, during the build process, moves these files to a directory so that they can be copied back into the mount afterwards.

However, it does not then remove these files - causing the warnings to continue to appear.

My proposed solution is that ece-tools deletes the old writeable directories after copying their contents, so that these false-alarm warnings do not appear in the logs.

Preconditions

1. Typical Magento Build, using the template. Out-of-the-box ECE-tools

Steps to reproduce

1. Deploy a Magento Instance

Expected result

1. I should not see errors that "The mount x has a path that overlaps with a non-empty folder"

Actual result

W: The mount '/app/etc' has a path that overlaps with a non-empty folder.
The content of the non-empty folder either comes from:

• your git repository (you may have accidentally committed files).
• or from the build hook.
  Please be aware that this content will not be accessible at runtime.

[BaDos]

@navarr hello,
it can be ignored because ece-tools uses the ./init folder to transfer files between phases.
it is an issue with low priority, the internal task will be created

[BaDos]

We have the internal task for that MCLOUD-8958