Randy Fay

Note that this capability is now built into `ddev npm` and `ddev yarn`, which may solve your problem. See the [HostWorkingDir](https://ddev.readthedocs.io/en/latest/users/extend/custom-commands/#hostworkingdir-annotation-container-commands-only) annotation. Does that do the job for you @shaal...

With that, you can now make a custom command that works the way you expect...

Those 2 commands... In your global .ddev...

https://github.com/drud/ddev/blob/3703a94a9b263a52c508a8e88be5da765787127e/pkg/ddevapp/global_dotddev_assets/commands/web/yarn#L1-L10

I'm not sure why all projects can't use the old method, but what you propose would be OK, except for the added complexity.

Thanks, will try to get it fixed up.

Thanks for the issue! I don't understand completely which command hangs (or if both do)? `ddev exec drush` and `ddev . drush` are the same thing. `ddev drush` is slightly...

So you never see this with `ddev exec drush cr`, but you see it with `ddev drush cr`, correct? But it seems your example was with `ddev exec drush cr`...

@ghalusa could you please do a `ddev debug test` and put the results in a gist on gist.github.com and provide the link here? Then please make sure you can replicate...

Interesting, could be a docker desktop issue then. I assume you're on latest 4.8.1... and yes, upgrading over time on docker desktop can have some interesting side-effects, and reset to...