Don't require homedir to be docker-shared (Warning message on ddev start "failed to copy root CA into docker volume" )

[rfay]

Describe the bug

macOS: It you docker-share a subdirectory of the homedir instead of the whole homedir, you get this complaint on start:

failed to copy root CA into docker volume: failed to StartContainer: API error (500): Mounts denied:
The path /Users/rfay/Library/Application Support/mkcert
is not shared from OS X and is not known to Docker.
You can configure shared paths from Docker -> Preferences... -> File Sharing.
See https://docs.docker.com/docker-for-mac/osxfs/#namespaces for more info.
.
, output=''
Pushed mkcert rootca certs to ddev-global-cache

I'm pretty sure this is not necessary. I also can't see where it breaks https; https seems to be trusted anyway.

Also, this is a warning message instead of an error.

To Reproduce

• In Docker's file sharing setup, do not share /Users (just share, for example, /Users/rfay/workspace
• ddev poweroff
• ddev start

Expected behavior

Should "just work"

Screenshots

Version and configuration information (please complete the following information):

• macOS Catalina
• Docker Desktop edge 2.3.3.0
• ddev version information v1.15.0

[rfay]

This is a result of https://github.com/drud/ddev/blob/9bb78d5ba819f3f9a1907995eb9e07de79d67417/pkg/ddevapp/ddevapp.go#L890-L897

We use a mount to push it in there; instead we can use docker cp I think.

[rfay]

Overall, the push should be done in StartDdevRouter() instead of in ddevapp.Start(). That's simpler and more appropriate. And it shouldn't be done if the router is already going, or even already exists.

The current code is pretty elegant as far as docker interactions go; they don't make it easy to push stuff into a volume.

I experimented with

1. Create container mounting ddev-global-cache
2. docker cp into /mnt/ddev-global-cache
3. Exec the chown/chmod to make those available permissions-wise.

But it was 3 steps instead of one. I wasnt' really happy with that.