Not able to switch to docker linux with premium worker
I'm following the sample provided by https://ci.appveyor.com/project/appveyor-tests/docker-ce/build/1.0.29 to run LCOWs and have a simple test for LCOWs:
https://github.com/mcred/appveyor-test
But the job: https://ci.appveyor.com/project/mcred/appveyor-test
Fails with "Failed to start the virtual machine 'MobyLinuxVM' because one of the Hyper-V components is not running."
How can I successfully run LCOWs?
Keyboard shortcuts
Generic
? | Show this help |
---|---|
ESC | Blurs the current field |
Comment Form
r | Focus the comment reply box |
---|---|
^ + ↩ | Submit the comment |
You can use Command ⌘
instead of Control ^
on Mac
1 Posted by Owen McDonnell on 26 Jul, 2019 05:20 PM
Since the post you linked to we've migrated users who want to run LCOW to
Windows Server 2019
(which is now enabled on your account).Can you try your build with
image: Windows Server 2019
added to your configuration and let us know if you still have problems.2 Posted by Derek Smart on 26 Jul, 2019 05:44 PM
Thanks for the input. I switched to `image: Windows Server 2019` and the build never seems to start. The following events take place:
2019-07-26 13:41:24.079 Information Decommissioning worker: b9bfc498e09344b5a5d43cd7cf797a16
2019-07-26 13:41:22.215 Information Check worker status in 180 seconds
2019-07-26 13:41:22.215 Information Provisioning worker of type 'Azure': cc7dc164d28345bd895cfbd5016f54b2
2019-07-26 13:41:22.122 Information Provision new worker in cloud 399: cc7dc164d28345bd895cfbd5016f54b2
2019-07-26 13:41:22.122 Information Decommission old worker in cloud 399: b9bfc498e09344b5a5d43cd7cf797a16
2019-07-26 13:41:22.107 Information Job re-scheduled to cloud 399
2019-07-26 13:41:22.107 Information Fetching clouds with name/group 'azure-westus' for account 1
2019-07-26 13:41:22.107 Information Trying to schedule job to the same cloud/group (attempt 1 of 5): azure-westus
2019-07-26 13:41:22.091 Warning Worker b9bfc498e09344b5a5d43cd7cf797a16 has not started the job - switching to failover cloud
2019-07-26 13:38:21.063 Information Check worker status in 180 seconds
3 Posted by Ilya Finkelshte... on 29 Jul, 2019 08:23 AM
Sorry for the late reply. It was an issue with this image, please see this incident. It should be good now. Please let us know if you have any issues.
4 Posted by Derek Smart on 29 Jul, 2019 03:15 PM
Thank you! This took care of it.