Azure Batch: Docker Compatible Windows Image Failed at Node Preparation

David Dong 0

Hi, I am trying to test an azure batch setup with a windows container. I noticed a few have been deprecated, but dsvm-win-2019 is available. In fact, it seems to be the only windows not marked EoL. When I start up a pool with this image, it fails with NodePreparation Error. Any way to resolve this? I was hoping to use something off the shelf, but my options are really constrained for a windows image. Thank you!

Pool Setup:

User's image

Pool's Node Error Message:

User's image

1 answer

Anveshreddy Nimmala 2,380 Reputation points Microsoft Vendor

2024-02-06T06:42:35.79+00:00
Hello @David Dong,Welcome to microsoft Q&A,Thankyou for posting your query here. The error message "unable to detect docker environment" typically indicates that the Batch node is not configured to run Docker containers. To run Docker containers on a Batch node, you need to install Docker and configure the Batch node to use the Docker engine. You can do this by creating a custom image that includes the Docker engine and using that image as the base image for your Batch pool. Install Docker on the base image. You can do this by downloading the Docker installer and running it in silent mode.

FROM microsoft/dotnet-framework:4.7.2-sdk # Download and install Docker ADD https://download.docker.com/win/static/stable/x86_64/docker-18.09.3.zip C:\\docker.zip RUN powershell -Command Expand-Archive -Path C:\\docker.zip -DestinationPath C:\\ ; \ Rename-Item -Path C:\\docker -NewName 'docker.exe' ; \ Move-Item -Path C:\\docker.exe -Destination C:\\Windows\\System32\\docker.exe

Build the custom image using the Docker command line docker build -t <image-name> . Use the custom image as the base image for your Batch pool. When creating the pool, specify the custom image as the imageReference and set the node Agent SKU Id to batch.node.windows amd64. az batch pool create \ --id mypool \ --vm-size Standard_D2_v2 \ --image-reference <image-name> \ --node-agent-sku-id "batch.node.windows amd64" \ --target-dedicated-nodes 1 \ --account-name mybatchaccount \ --account-endpoint https://mybatchaccount.region.batch.azure.com \ --access-key mybatchaccountkey Hope this helps you. please consider accepting the answer to help increase visibility of this question for other members of the Microsoft Q&A community. If not, please let us know what is still needed in the comments so the question can be answered. Thank you for helping to improve Microsoft Q&A!.
Please sign in to rate this answer.
David Dong 0 Reputation points

2024-02-06T15:31:34.8166667+00:00

Hi @Anveshreddy Nimmala thanks for the help! I was choosing from the marketplace with supported images -- az batch pool supported-images list Below is one of the entries. Does it mean docker is not supported for this windows image and needs to be corrected? And do I now have to create my own custom image?

{ "batchSupportEndOfLife": null, "capabilities": [ "DockerCompatible" ], "imageReference": { "exactVersion": null, "offer": "dsvm-win-2019", "publisher": "microsoft-dsvm", "sku": "winserver-2019", "version": "latest", "virtualMachineImageId": null }, "nodeAgentSkuId": "batch.node.windows amd64", "osType": "windows", "verificationType": "unverified" },

Anveshreddy Nimmala 2,380 Reputation points Microsoft Vendor

2024-02-07T05:15:24.3066667+00:00

Hello @David Dong, thankyou for replying back. The output of the az batch pool supported-images list command shows that the DSVM Windows 2019 image is Docker Compatible, which means that it should be able to run Docker containers. However, it's possible that the image does not have Docker installed by default, which could be causing the NodePreparation Error. If you want to use the DSVM Windows 2019 image and run Docker containers, you can create a custom image that includes Docker and use that image as the base image for your Batch pool. This will ensure that Docker is installed and configured correctly on the nodes in your pool you can try installing Docker on the nodes in your Batch pool manually using a startup task. you can create a startup task that runs a script to download and install Docker on the nodes.

"startTask": { "commandLine": "powershell.exe -ExecutionPolicy Unrestricted -File install-docker.ps1", "waitForSuccess": true, "userIdentity": { "autoUser": { "scope": "pool", "elevationLevel": "admin" } } }

The install-docker.ps1 script should contain the commands to download and install Docker on the node.

# Download the Docker installer Invoke-WebRequest -Uri "https://download.docker.com/win/stable/Docker%20Desktop%20Installer.exe" -OutFile "Docker Desktop Installer.exe" # Install Docker Start-Process -FilePath "Docker Desktop Installer.exe" -ArgumentList "/S" -Wait

Hope this helps you. please consider accepting the answer to help increase visibility of this question for other members of the Microsoft Q&A community. If not, please let us know what is still needed in the comments so the question can be answered. Thank you for helping to improve Microsoft Q&A!.

David Dong 0 Reputation points

2024-02-08T18:18:53.45+00:00

Yes, it seems like this windows image doesn't have docker with windows-containers installed by default. I tried adding the startup task to install docker from the interface from your advice like so:

I still get the node preparation error. Does this mean I'm limited to manually creating a custom vm image from Compute Gallery? Compared to the linux-based batch pool setup, I was hoping it would be like the dsvm ubuntu-hpc offering where it works out of the box

Update: This startup task does not seem right at all. This is not a real uri for installing docker desktop and I can't install docker desktop after testing by manually creating a VM with this image.

Anveshreddy Nimmala 2,380 Reputation points Microsoft Vendor

2024-02-09T04:24:12.4366667+00:00

Hello @David Dong, thankyou for replying back. If you have added a startup task to install Docker on the nodes in your Batch pool and you are still encountering the NodePreparation error, it's possible that there is an issue with the startup task or the script that it is running. To troubleshoot the issue, you can try running the script manually on one of the nodes in your Batch pool to see if it installs Docker correctly. You can also check the Batch service logs to see if there are any errors or warnings related to the startup task or the script. If you are still unable to resolve the issue, you may need to create a custom VM image that includes Docker and use that image as the base image for your Batch pool. This will ensure that Docker is installed and configured correctly on the nodes in your pool. I understand that it would be more convenient if the DSVM Windows 2019 image worked out of the box like the DSVM Ubuntu-HPC offering. However, it's possible that the Windows image has different requirements or limitations that make it more difficult to use with Docker. Creating a custom VM image will give you more control over the environment and ensure that it meets your specific requirements.

David Dong 0 Reputation points

2024-02-09T16:29:44.2433333+00:00

Ok, thanks. It seems like it's the custom vm image route. Thanks for the assistance!

Anveshreddy Nimmala 2,380 Reputation points Microsoft Vendor

2024-02-12T04:00:09.2366667+00:00

Hello @David Dong, thankyou for replying back. please consider accepting the answer to help increase visibility of this question for other members of the Microsoft Q&A community. If not, please let us know what is still needed in the comments so the question can be answered.

Anveshreddy Nimmala 2,380 Reputation points Microsoft Vendor

2024-02-13T03:56:03.99+00:00

Hello @David Dong, thankyou for replying back. please consider accepting the answer to help increase visibility of this question for other members of the Microsoft Q&A community. If not, please let us know what is still needed in the comments so the question can be answered.

Anveshreddy Nimmala 2,380 Reputation points Microsoft Vendor

2024-02-15T04:55:04.7766667+00:00

Hello @David Dong, We noticed that you rated an answer as not helpful. I have provided an answer with the relevant details to make this a positive experience for you. To install Docker 25.0.3 on a Windows Server 2019 node in your Batch pool, you can use a startup task that downloads and installs the Docker EE installer. Here's an example of what the startup task might look like:

"startTask": { "commandLine": "powershell.exe -ExecutionPolicy Unrestricted -File install-docker.ps1", "waitForSuccess": true, "userIdentity": { "autoUser": { "scope": "pool", "elevationLevel": "admin" } } }

The install-docker.ps1 script should contain the commands to download and install docker-25.0.3 on the node.

# Download the Docker EE installer Invoke-WebRequest -Uri "https://download.docker.com/win/static/stable/x86_64/docker-25.0.3.zip" -OutFile "docker-25.0.3.zip" # Extract the installer Expand-Archive -Path "docker-25.0.3.zip" -DestinationPath "C:\docker-25.0.3" # Install Docker EE C:\docker-25.0.3\InstallDocker25.0.03.ps1

After the startup task completes, you should be able to run Docker containers on the nodes in your Batch pool.We value your feedback. If my answer is helpful, would you be so kind to re-evaluate your feedback, accept my answer and upvote the same please.
Sign in to comment