Cavalcade container fails to start with error on first startup

[kadamwhite]

Steps to reproduce:

1. On an M1 Mac, clone the Altis skeleton into a new directory:

   composer create-project altis/skeleton altis-sandbox

2. cd into the newly-created directory and run composer server start. You will see this error, and the command will exit without starting all containers:

   Error response from daemon: failed to mkdir /var/lib/docker/volumes/altis-sandbox_tmp/_data/pear: mkdir /var/lib/docker/volumes/altis-sandbox_tmp/_data/pear: file exists

Full `composer server start` command output

``` Starting... [+] Running 1/1 ⠿ Container altis-proxy Started 0.4s [+] Running 19/20 ⠿ Network altis-sandbox_default Created 0.0s ⠿ Volume "altis-sandbox_tmp" Created 0.0s ⠿ Volume "altis-sandbox_s3" Created 0.0s ⠿ Volume "altis-sandbox_db-data" Created 0.0s ⠿ Volume "altis-sandbox_es-data" Created 0.0s ⠿ Volume "altis-sandbox_socket" Created 0.0s ⠿ Container altis-sandbox-es Created 0.2s ⠿ Container altis-sandbox-cognito Created 0.1s ⠿ Container altis-sandbox-tachyon Created 0.1s ⠿ Container altis-sandbox-s3 Created 0.1s ⠿ Container altis-sandbox-pinpoint Created 0.2s ⠿ Container altis-sandbox-redis Created 0.1s ⠿ Container altis-sandbox-db Created 0.1s ⠿ Container altis-sandbox-mailhog Created 0.1s ⠿ Container altis-sandbox-xray Created 0.1s ⠿ Container altis-sandbox-s3-sync Created 0.1s ⠹ Container altis-sandbox-cavalcade Creating 0.2s ⠿ Container altis-sandbox-php Created 0.1s ⠿ Container altis-sandbox-kibana Created 0.1s ⠿ Container altis-sandbox-nginx Created 0.1s Error response from daemon: failed to mkdir /var/lib/docker/volumes/altis-sandbox_tmp/_data/pear: mkdir /var/lib/docker/volumes/altis-sandbox_tmp/_data/pear: file exists Services failed to start successfully. ```

3. Run composer server start once more. Server now actually starts.

I expected to see no error, and for the server to start first-time.

Acceptance criteria:

• [ ] composer server start correctly initializes Cavalcade container on first use when creating a new Docker environment.

[roborourke]

Is this still happening consistently?