Agent is not responding with Windows Docker(Generated by Packer)

[nbyavuz]

Hi,

I am trying to create Windows docker images with Packer but when I used these images(nbyavuz/mingw-images) on Cirrus CI, task errors with: 'Agent is not responding' after 15 minutes. There is a similar issue: #947. Is the thing I am experiencing similar to this issue or is there something else?

I am using this packer config for creating Windows docker images.

Expected Behavior

The container should start.

Real Behavior

The container is terminated after 15 minutes of wait time with the error message 'Agent is not responding': https://cirrus-ci.com/task/5850061943341056

Related Info

This is a (tick one of the following):

• Website issue
  • Link to page:
• Task issue
  • OS: Windows
  • Task name: Windows - Server 2019, MinGW64 - Meson - Cirrus CI
  • Script/cache name (if applies):

[fkorotkov]

I think it might be similar issue to #970 (comment)

Are you sure your VM is respecting startup/shutdown scripts?

[nbyavuz]

I thought we needed to respect startup/shutdown scripts when we created custom VM images but in this case we are using official Windows docker images(mcr.microsoft.com/windows/servercore:ltsc2022), running some scripts, then publishing Windows docker images to the dockerhub (could this be the problem? We are not pushing images to the Google Cloud, instead we pushed them to dockerhub) like you did at https://github.com/cirruslabs/docker-images-windows. However instead of using docker commands, we are doing these with the help of Packer.

[fkorotkov]

Oh. Got it. Than it seems the image is so huge it's not getting downloaded or unarchived in 15 minutes (that's the timeout). Or maybe ltsc2022 which is not cached. We do run windows containers on 2019 hosts and haven't still upgraded to 2022.

Let me check if we now can add 2022 support. Last time I checked it in July it was supproted pretty bad.

[nbyavuz]

Thanks!