search

XedinUnknown / red-acre-test-a-1

Red Acre - Test A-1
GNU General Public License v2.0
0 stars 0 forks source link

invalid mount config for type "bind": bind source path does not exist #4

Open chrisbartolora opened 1 year ago

chrisbartolora commented 1 year ago

binding fails, ./wordpress path doesn't exist...

XedinUnknown commented 1 year ago

Hi @chrisbartolora, and thanks for reporting this!

I was unable to reproduce the symptoms you have described. The directory is created by Docker, because it binds the internal directory into it so that we can inspect WP code, and use debugging tools with it. I'm not exactly sure how you were able to get this error; would you be able to describe the steps you took, please? Here's what I did:

  1. Purge all local Docker data. I use Docker Desktop 4.21.1 (114176), which has a button for that. If your GUI doesn't support that or you use only CLI, here's a guide that explains how you may be able to achieve this manually.

  2. Follow the steps in the readme to the letter. I used a fresh directory. I also encountered issue #3 during step 4, but after applying the fix I was able to continue normally. I skipped 5, because I already had the entry in my hosts file. After the automatic installation and configuration of WordPress, the files of which I could immediately see in the newly created by Docker wordpress directory, I was able to access the website on http://red-acre-test-a-1.myhost, as expected.

    One notable thing here is that some of the website's presentation was broken for me, beause the images checked out by Git were corrupt. This has happened before, and I re-cut the images again and committed the fixed ones - but it seems that whatever I do, once they go through the VCS they get corrupted again. Please find them attached here; you can use these to replace the likely corrupted files in modules\theme\frontend\img, which should restore the presentation it did for me.

Could you try doing the same too, please? This could help eliminate any local issues that your environment may have. It could also be a platform issue: I'm on Windows 11/WSL2; what platform are you using? Mac is known to have many Docker-related issues; different to the ones that WSL is known to have. At the same time, this setup is part of wp-oop/plugin-boilerplate, and many plugins were created from it, and they worked for my colleagues on MacOS just the same, as I took extra care to test with that platform when possible.

Please let me know how it goes! If you are unable to fix the issue with the help of my suggestions and links, I'd be very happy to do a screen-sharing session or even walk you through it in person. I believe that this project demonstrates many great features and helpful knowledge that results from many mistakes.