Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Log shows errors that mount overlaps with non-empty folder #812

Open
navarr opened this issue Aug 2, 2022 · 2 comments
Open

Log shows errors that mount overlaps with non-empty folder #812

navarr opened this issue Aug 2, 2022 · 2 comments

Comments

@navarr
Copy link
Member

navarr commented Aug 2, 2022

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
Copy link
Contributor

BaDos commented Aug 3, 2022

@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
Copy link
Contributor

BaDos commented Aug 31, 2022

We have the internal task for that MCLOUD-8958

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Ready for Grooming
Development

No branches or pull requests

2 participants