I created a Windows Docker image that includes some dependencies, including the Windows SDK. The issue I'm having is that when I run the container from this image on the machine where it was built, it works perfectly. However, when I save the image and load it onto a different machine, the container fails to operate as expected. I discovered that if I manually install the Windows SDK within a running container on the second machine, it still doesn't work. Yet if I attempt to build another image using the original as a base, I'm still facing issues. When I try to execute mt.exe, there's no output, and the status code I receive is -1073741819, which translates to an access violation. I've already confirmed that both the VC redistributable and .NET runtime are installed. Can anyone offer insight into what might be going wrong?
2 Answers
Have you tried providing more details in your Dockerfile? Sometimes, a simple oversight can lead to issues, particularly with what dependencies you’re including. Make sure you’re specifying all necessary installations clearly in your file.
Windows containers can definitely be tricky! A common issue is version mismatches between the build and runtime environments. If your original image was built on a specific version of Windows Server, make sure the second machine is running the exact same version. If there's a build discrepancy, even a minor one, it could cause the container to malfunction.
That's a good point! I had a similar issue with build versions once; ensuring they matched saved me a lot of headaches.
Thanks for the tip! I'll check the server versions on both machines.