Skip to content
New issue

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

Docker build image task failed on VSTS (UtilityVM: the system cannot find the path specified) #6510

Closed
ChristopheLav opened this issue Feb 23, 2018 · 2 comments

Comments

Projects
None yet
5 participants
@ChristopheLav
Copy link

commented Feb 23, 2018

Environment

Using VSTS
Account name: devops-sandbox
Team Project: Phoenix
Build Definition: Phoenix Portal Container - CI
Build number: 20180223.6 or 20180222.1
Agent: Hosted VS2017

Issue Description

I created a new .NET Core project (default Web template) without any customization with Windows container support. Everything run on my computer, but failed on VSTS.

I'm using the VSTS build docker template to build and push.

Error logs

==============================================================================
Task : Docker
Description : Build, tag, push, or run Docker images, or run a Docker command. Task can be used with Docker or Azure Container registry.
Version : 0.3.4
Author : Microsoft Corporation
Help : More Information

"C:\Program Files\Docker\docker.exe" build -f D:\a\1\s\Phoenix.Portal\Dockerfile -t iaphoenix.azurecr.io/phoenix-portal:10 D:\a\1\s\Phoenix.Portal
Sending build context to Docker daemon 2.44MB

Step 1/3 : FROM microsoft/aspnetcore:2.0-nanoserver-1709 AS base
2.0-nanoserver-1709: Pulling from microsoft/aspnetcore
407ada6e90de: Pulling fs layer
3cb15ab58a2c: Pulling fs layer
e1cc03b9b8eb: Pulling fs layer
3a704066cde0: Pulling fs layer
e27752919d66: Pulling fs layer
0df844d28249: Pulling fs layer
6758300bb1c4: Pulling fs layer
ef9595e18bd2: Pulling fs layer
5818114c861e: Pulling fs layer
e27752919d66: Waiting
0df844d28249: Waiting
6758300bb1c4: Waiting
ef9595e18bd2: Waiting
5818114c861e: Waiting
3a704066cde0: Waiting
e1cc03b9b8eb: Verifying Checksum
e1cc03b9b8eb: Download complete
3cb15ab58a2c: Verifying Checksum
3cb15ab58a2c: Download complete
3a704066cde0: Verifying Checksum
3a704066cde0: Download complete
407ada6e90de: Verifying Checksum
407ada6e90de: Download complete
0df844d28249: Verifying Checksum
0df844d28249: Download complete
e27752919d66: Download complete
6758300bb1c4: Verifying Checksum
6758300bb1c4: Download complete
ef9595e18bd2: Verifying Checksum
ef9595e18bd2: Download complete
5818114c861e: Verifying Checksum
5818114c861e: Download complete
failed to register layer: re-exec error: exit status 1: output: ProcessUtilityVMImage C:\ProgramData\docker\windowsfilter\ec1d68d8dc35d6260f8feca6accd687d0ccb16cb36e1803d47ca0a3e6a9fd13f\UtilityVM: The system cannot find the path specified.
C:\Program Files\Docker\docker.exe failed with return code: 1


Finishing: Build an image


@Hammatt

This comment has been minimized.

Copy link

commented Feb 28, 2018

I'm running into the same issue trying to build an IoT Edge Module (these modules are windows container images) in VSTS.
We're using the same type of agent, Hosted VS2017.

2018-02-27T21:06:31.3601916Z Step 1/5 : FROM microsoft/dotnet:2.0.0-runtime-nanoserver-1709
2018-02-27T21:06:31.9657795Z 2.0.0-runtime-nanoserver-1709: Pulling from microsoft/dotnet
2018-02-27T21:06:32.1553255Z 407ada6e90de: Pulling fs layer
2018-02-27T21:06:32.1554008Z ad09b0550b6c: Pulling fs layer
2018-02-27T21:06:32.1554566Z ae907c318f69: Pulling fs layer
2018-02-27T21:06:32.1554821Z 1e4026051ed1: Pulling fs layer
2018-02-27T21:06:32.1818066Z 1e4026051ed1: Waiting
2018-02-27T21:06:32.7713175Z ad09b0550b6c: Verifying Checksum
2018-02-27T21:06:32.7713569Z ad09b0550b6c: Download complete
2018-02-27T21:06:33.0193890Z ae907c318f69: Verifying Checksum
2018-02-27T21:06:33.0198409Z ae907c318f69: Download complete
2018-02-27T21:06:33.1779531Z 1e4026051ed1: Verifying Checksum
2018-02-27T21:06:33.1779905Z 1e4026051ed1: Download complete
2018-02-27T21:06:33.3120772Z 407ada6e90de: Verifying Checksum
2018-02-27T21:06:33.3121156Z 407ada6e90de: Download complete
2018-02-27T21:07:06.3572375Z failed to register layer: re-exec error: exit status 1: output: ProcessUtilityVMImage C:\ProgramData\docker\windowsfilter\2ec043519f3a0068f436d494461be7c8215b2c9c607536a964ffe7db3fea2b0f\UtilityVM: The system cannot find the path specified.
2018-02-27T21:07:06.3833395Z ##[error]C:\Program Files\Docker\docker.exe failed with return code: 1
@ChristopheLav

This comment has been minimized.

Copy link
Author

commented Mar 3, 2018

I found maybe an explication about this error: VSTS agents seem not support nanoserver-1709 actually. Maybe this will change with the next version 1803.

See details here: microsoft/azure-pipelines-agent#1393

When I setup and host a custom agent on a machine on Azure, it's working. So it's not a bug with this task. I close this issue. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.