ISSUE TYPE

• Documentation

SUMMARY

Ambiguity with xDebug on Docker Toolbox setup

Goal

To get xDebug working properly on Docker Toolbox, & clarify the docs to make it easier for others.

I've been struggling for several hours, still unsuccessfully, to get xDebug working on Docker Toolbox, based on the docs

As noted in #1258 there is sense in checking for hash sums of downloaded binaries docker, docker-compose, docker-machine, winpty.exe for security reasons.

Fin should also issue a warning before downloading then that it is going to but them into ~/.docksal folder and will not overwrite any system binaries.

Based on the current README my expectation was that the certificate_file, certificate_key_file and certificate_chain_file directives needed to point to local (on the ansible control node) which would get installed by the role.

It turns out that the paths are entered in the vhosts.conf.
No files are deployed so the playbook needs to handle that outisde this role.

I believe it would be useful

I used nand-sata-install to copy the filesystem over to system on sata / usb whilst choosing btrfs as the filesystem.

After using softy to install docker, the docker daemon wouldn't start. All that was needed was to add /etc/docker/daemon.json as mentioned in the [docker docs](https://docs.docker.com/storage/storagedriver/btrfs-driver/#configure-docker-to-use-the-btrfs-storage-dri