We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Steps to reproduce:
composer create-project altis/skeleton altis-sandbox
cd
composer server start
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
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.
I expected to see no error, and for the server to start first-time.
Acceptance criteria:
The text was updated successfully, but these errors were encountered:
Is this still happening consistently?
Sorry, something went wrong.
No branches or pull requests
Steps to reproduce:
cd
into the newly-created directory and runcomposer server start
.You will see this error, and the command will exit without starting all containers:
Full `composer server start` command output
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.The text was updated successfully, but these errors were encountered: