Closed marcelvos1 closed 3 years ago
Hi, when the docker start fails, there probably is something wrong with the creation of the image.
this is the error you need to look at: The virtual machine could not be started because a required feature is not installed.
Docker isn't too descriptive, unfortunately.
Did you try to run maintenance on the machine (there is an ALOps step for that as well). Just clear as much as possible, and re-run the pipeline.. .
Hi Waldo, Yes I run the maintenace multiple times.
FYI, we installed a new server and the problems are gone. The Azure VM still exist with the error. So we can further now but if we can investigate the problem it will be nice.
The virtual machine could not be started because a required feature is not installed. <- I checked also the windows features and install it again, but without any result
@marcelvos1 just a guess, maybe you got a Windows update which forced you to use hyperv isolation now but the Azure VM doesn't support it? Do you still have logs from successful runs? And which Azure VM size are you using?
Hi Marcel,
As much as I want to get to the bottom of it, I can't put too much time into investigation infrastructure/docker-related problems on the agent. I hope you understand.
As we are using BcContainerHelper, could you please try to do a simple New-BcImage
on the faulty server and tell me the results?
@marcelvos1 just a guess, maybe you got a Windows update which forced you to use hyperv isolation now but the Azure VM doesn't support it? Do you still have logs from successful runs? And which Azure VM size are you using?
I will check this.
Hi Marcel,
As much as I want to get to the bottom of it, I can't put too much time into investigation infrastructure/docker-related problems on the agent. I hope you understand.
As we are using BcContainerHelper, could you please try to do a simple
New-BcImage
on the faulty server and tell me the results?
Ok. No problem. I will test this and share the result with you
Dear @marcelvos1 ,
Please check our latest release v1.443.2509 which might address this issue.
Kind regards
Hi @AdminHodor , Sorry for my late response. We have installed the server again and problem was gone. So unfortunately I don't know what exactly caused the problem. This issue can be closed.
Since a couple of days we run in the error: Error response from daemon: pull access denied for myimage, repository does not exist or may require 'docker login': denied: requested access to the resource is denied.
This happens for all our build pipelines. We have update the build server, checked if docker is installed/enabled, Hyper-V is enabled and all windows features are installed. We run also again the PowerShell script to install the windows features and docker, but no result. Today we tested the builds on a Azure VM that we use as a backup VM, but on this VM the build gives the same error message.
Thanks for help.
the used yaml
the output
Create Docker Image
Start Docker Container
Screenshots