ddev install and database issue

Hi @gto1.

I think it's a problem with DDEV rather than Drupal CMS. I get the same error with a lot of the sites I run locally.

I find that running ddev start again fixes the issue. Mutagen doesn't take as much time to run the second time.

I know it's annoying, but it's a work-around that gets the site running while the DDEV folks find out what the problem is.

@gto1 have you run the command (ddev mutagen st drupal-cms -1) that was recommended in the screenshot you've provided? and if you did, could you provide the output? and if not could you run the command if you run into the problem the next time?

but i am unable to reproduce the problem. i've went through the steps to reproduce and everything worked as expected. i've tested with ddev HEAD which is one or two commits ahead of the latest version of ddev (1.24.0) on macos with lima. and one detail i've noticed, you've tested with ddev 1.23.3... so it might be worth a try to update to the latest version of ddev first and retry with that?

There are a few problems here.

1. Please use DDEV's `drupal11` or `drupal` project type. (`ddev config --project-type=drupal --docroot=web`). If you had done that, the database information would have been filled in for you automatically,, and you wouldn't have had to know what the database settings were.
2. Please use the current version of DDEV, v1.24.0, rather than an older one, especially when debugging problems.
3. The database settings used with DDEV are explained many places, including the FAQ, "How can I connect to my database", see https://ddev.readthedocs.io/en/stable/users/usage/faq/#how-can-i-connect.... In DDEV, from the web container, the hostname is "db" (NOT localhost), username "db", password "db" and database "db". (not "test", although you could create one named "test", but we'll leave that for another time. (Read more about databases at https://ddev.readthedocs.io/en/stable/users/usage/database-management/ )

Happy to help you get farther along in #ddev in Drupal slack or DDEV's discord, https://discord.com/invite/5wjP76mBJD

I just tried this and it worked fine.

Please make sure you start by creating an empty directory, *then* unzip the zipball into that empty directory. Then `cd` into the directory and `ddev start`.

For example:

mkdir my-drupal-cms && cd my-drupal-cms
unzip ~/Downloads/drupal-cms.zip
ddev start
ddev launch

The mutagen sync should take less than 30 seconds in this situation.

@john-cook, I imagine you have a different problem, and I'd be happy to help you chase it. If your mutagen sync takes forever, it normally means you have huge files some place that `upload_dirs` doesn't know about.

Hi @gto1,
The issue seems to stem from the web container failing to pass its health check, causing the setup process to stop.
Run the following command to check the detailed logs for the web container:
ddev logs ddev-drupal-cms-web
These logs will provide insights into the root cause of the problem, such as missing PHP extensions, filesystem permission issues, or configuration errors.

Please share the logs here so we can review them and suggest the next steps to resolve the issue.
Thanks!

Thanks All, much appreciated. #6 worked.

📌 Change zipball to put drupal cms in subdirectory Active should fix this for the future. Closing this one out now.