question

sinbat-7746 avatar image
0 Votes"
sinbat-7746 asked srbose-msft commented

Containers do not work on a VM deployed from the image 'Windows Server 2019 Datacenter with containers' in a domain network

Dear gurus. We have a VM deployed from a marketplace image 'Windows Server 2019 Datacenter with containers' and joined to the domain network in Azure. Unfortunately, when I am trying to run Docker images the cmd console just hangs. And then I am getting the error below:
141741-docker-error.png

Would you please explain\advise whether it is expected behavior when such a VM added to a domain VNET?


azure-virtual-machines
docker-error.png (7.8 KiB)
· 3
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

@sinbat-7746 , thank you for your question. Can you please share what docker image you were trying to run, the amount of compute resources associated with the VM (Memory and CPU) and more details from the Event?

Can you try restarting the docker service on the VM using Restart-Service docker from Windows PowerShell or cmd and trying again?

In the meanwhile, here is a similar incident:

0 Votes 0 ·

Hi @srbose-msft , thank for you answer.
So answering your questions one by one:

  • Can you please share what docker image you were trying to run? -> different images, including the ones provided together with a Windows VM image. I tried to run commands 'docker run <image>', 'docker run -it <image>', 'docker run <image> --isolation=process' and 'docker run <image> --isolation=hyperv' with the same result.
    142916-image.png

  • the amount of compute resources associated with the VM (Memory and CPU) -> the VM size is D2s_v3 (2vcpus, 8GiB memory)

  • more details from the Event -> all the events shown on the screenshot bellow occurred sequentially.
    143011-list-of-errors.png


Can you try restarting the docker service on the VM using Restart-Service docker from Windows PowerShell or cmd and trying again? -> I tried all steps which you enumerated, even tried to cleanup Docker stuff on a VM afterwards using a script from the link below, but no success.



0 Votes 0 ·
image.png (8.9 KiB)
list-of-errors.png (64.4 KiB)

@sinbat-7746 , thank you for your response. Based on the information shared, the best course of action would be to open a Microsoft technical support request. Also, once you get the issue fixed, request you to reply back here on the thread with the resolution steps for the benefit of the community.

0 Votes 0 ·
LimitlessTechnology-2700 avatar image
0 Votes"
LimitlessTechnology-2700 answered

Hi there,

Make sure you are running the correct version. Windows Server 2016 and Windows 10 Anniversary Update (both version 14393) were the first Windows releases that could build and run Windows Server containers. Containers built using these versions can run on newer releases.

This might help out in determining it https://docs.microsoft.com/en-us/virtualization/windowscontainers/deploy-containers/version-compatibility?tabs=windows-server-2022%2Cwindows-10-21H1



--If the reply is helpful, please Upvote and Accept it as an answer--

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

sinbat-7746 avatar image
0 Votes"
sinbat-7746 answered sinbat-7746 edited

Hi, thank for your answer. Here is a Windows OS version which I used - 1809. I tried to run Windows containers on a such VM spinning up in a trial Azure subscription and they worked flawlessly.
142019-docker-error2.png



docker-error2.png (5.9 KiB)
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.