Sample Data Doesn't install

[artmuscode]

Description
When running bin/init processes looks to enable/install required modules but no data actually populates the DB.

Steps To Reproduce

1. MAC M4 Newest MacOS
2. Running bin/init doesn't install or deploy sample data

Expected Result
Sample Data installed/deployed

Actual Result
DB doesn't get populated by the sample data

[dosubot]

This is a known issue. The key insight is that sample data installation is a two-step process:

1. bin/magento sampledata:deploy - Only registers/enables the sample data modules
2. bin/magento setup:upgrade - Actually populates the database with data

Your symptom (modules enabled but no data) suggests sampledata:deploy succeeded but setup:upgrade either failed silently or didn't complete the data population phase. This matches similar reports of intermittent sample data issues.

Troubleshooting steps:

1. Check the logs during bin/init to see if setup:upgrade completed without errors
2. Try running manually after init completes:

   bin/magento setup:upgrade
   bin/magento setup:di:compile
   bin/magento setup:static-content:deploy -f
   

3. Fix permissions: bin/fixowns && bin/fixperms
4. Clear caches

For Apple Silicon (M4): Ensure you're using docker-magento version 40.0.0 or higher, which officially supports Apple Silicon. Earlier versions have ARM architecture issues.

Could you share any error messages from the setup:upgrade output during bin/init?

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}

   

[artmuscode]

I'm getting no error messages during the process.

[dosubot]

Silent failures are a known pattern with sample data installation. A few things to check:

1. Verify sample data status:

bin/clinotty mysql -e "SELECT COUNT(*) FROM catalog_product_entity;"

A low count (0-10) confirms data didn't populate.

2. Check Docker resources: Sample data needs at least 6GB RAM allocated to Docker. On Mac, go to Docker Desktop → Settings → Resources and verify memory allocation.

3. Check Magento logs for hidden errors:

bin/clinotty cat var/log/exception.log
bin/clinotty cat var/log/system.log

4. Try running manually:

bin/magento setup:upgrade
bin/magento sampledata:deploy
bin/magento setup:upgrade
bin/magento setup:di:compile
bin/magento setup:static-content:deploy -f

5. Verify auth.json: Ensure your Magento Marketplace credentials are correct in auth.json - invalid credentials can cause silent failures on M-series Macs.

How much RAM do you have allocated to Docker?

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}

   

[artmuscode]

Seems to have helped. Thanks, Close the issue.