Bitrise Build Issue Report template
Description of the issue
We are using docker to run our service to do E2E testing. This has been working for us fine before this weekend where de discovered that docker-machine is complaining about virtualization not being enabled in the BIOs .
+ /Users/vagrant/git/scripts/bitrise/bitrise.setupApi.sh + setup_api + docker-machine create --driver virtualbox --virtualbox-memory 1500 default Creating CA: /Users/vagrant/.docker/machine/certs/ca.pem Creating client certificate: /Users/vagrant/.docker/machine/certs/cert.pem Running pre-create checks... Error with pre-create check: "This computer doesn't have VT-X/AMD-v enabled. Enabling it in the BIOS is mandatory"
Before the update it looked like:
+ /Users/vagrant/git/scripts/bitrise/bitrise.setupApi.sh + setup_api + docker-machine create --driver virtualbox --virtualbox-memory 1500 default Creating CA: /Users/vagrant/.docker/machine/certs/ca.pem Creating client certificate: /Users/vagrant/.docker/machine/certs/cert.pem Running pre-create checks... (default) Unable to get the latest Boot2Docker ISO release version: failure getting a version tag from the Github API response (are you getting rate limited by Github?) Creating machine... (default) Unable to get the latest Boot2Docker ISO release version: failure getting a version tag from the Github API response (are you getting rate limited by Github?) (default) Copying /Users/vagrant/.docker/machine/cache/boot2docker.iso to /Users/vagrant/.docker/machine/machines/default/boot2docker.iso... (default) Creating VirtualBox VM... (default) Creating SSH key... (default) Starting the VM... (default) Check network to re-create if needed... (default) Found a new host-only adapter: "vboxnet0" (default) Waiting for an IP... Waiting for machine to be running, this may take a few minutes... Detecting operating system of created instance... Waiting for SSH to be available... Detecting the provisioner... Provisioning with boot2docker... Copying certs to the local machine directory... Copying certs to the remote machine... Setting Docker configuration on the remote daemon... Checking connection to Docker... Docker is up and running! To see how to connect your Docker Client to the Docker Engine running on this virtual machine, run: docker-machine env default ++ docker-machine env default + eval export 'DOCKER_TLS_VERIFY="1"' export 'DOCKER_HOST="tcp://192.168.99.100:2376"' export 'DOCKER_CERT_PATH="/Users/vagrant/.docker/machine/machines/default"' export 'DOCKER_MACHINE_NAME="default"' '#' Run this command to configure your shell: '#' eval '$(docker-machine' env 'default) ' ++ export DOCKER_TLS_VERIFY=1 export DOCKER_HOST=tcp://192.168.99.100:2376 export DOCKER_CERT_PATH=/Users/vagrant/.docker/machine/machines/default export DOCKER_MACHINE_NAME=default ++ DOCKER_TLS_VERIFY=1 ++ DOCKER_HOST=tcp://192.168.99.100:2376 ++ DOCKER_CERT_PATH=/Users/vagrant/.docker/machine/machines/default ++ DOCKER_MACHINE_NAME=default
Xcode 10.2 Mojave
Which build Step causes the issue and which version of the step?
- Does a “Rebuild” help? (You can trigger a rebuild from the Build’s page, by clicking the “Rebuild” button in the top right corner of a finished build) : NO
Does a rebuild without caches help? (You can remove the
Cache:Pushsteps temporarily to not to use the cache, or you can delete all the caches on the
Settingstab of the app. : NO
- Does the issue happen sporadically, or every time? : every time
- Does upgrading the build Step to the latest version help? : NO
- When did the issue start? : Last working on June 7th, noticed on June 11th