Okay, it sounds like AMP recognizes the datastore correctly but maybe Docker’s mount permissions are causing files to be partially written. A classic “It’s fine… BUT IS IT?” moment. ![]()
Let’s test another angle—does AMP spit out any more detailed logs about this datastore issue? You can check:
-
In the AMP GUI:
- Right-click on the instance with the issue and select “View Logs.”
- Look for entries in there that scream “Permission Denied” or related errors when it tries to create/write files during the setup.
-
If you don’t see useful info, try AMP’s Diagnostics Tool:
- Go to AMP → Support → Diagnostics, and hit the “Copy data to clipboard” button.
- Paste what it shows here (no sensitive info like passwords or private keys, though).
Those logs might spill the tea about why Docker is ignoring some files. ![]()