简体   繁体   English

Windows Docker容器中未启动32位进程

[英]32-bit process not started in windows docker container

I have a simple 32 bit commandline application (CPP application), which is started using C# in ASP.NET Core. 我有一个简单的32位命令行应用程序(CPP应用程序),它是使用ASP.NET Core中的C#启动的。

System.Diagnostics.Process.Start("Application");

It is working fine in 32-bit/64-bit application when testing on serveral windows OS (32-bit/64-bit). 在服务器Windows OS(32位/ 64位)上进行测试时,它在32位/ 64位应用程序中正常运行。

When running the application in docker container, it does not launch the 32-bit application. 在Docker容器中运行应用程序时,它不会启动32位应用程序。

If I use the simple 64-bit applcation, then it is launching properly. 如果我使用简单的64位应用程序,那么它将正常启动。 But I could not build my CPP application to 64-bit, as its dependencies are 32-bit. 但是我无法将我的CPP应用程序构建为64位,因为它的依赖项是32位。

Docker container : windows/amd64 Docker容器:Windows / amd64

Can anyone please help me to overcome this? 谁能帮我克服这个困难? I'm new to docker. 我是Docker的新手。

There is no supported way of running 32-bit applications in containers. 没有在容器中运行32位应用程序的受支持方法。 You might find some obscure ways to create 32-bit containers though. 但是,您可能会发现一些晦涩的方法来创建32位容器。 But it involves a lot of work and such a container would only support 32-bit applications. 但这涉及许多工作,并且这样的容器支持32位应用程序。

Cheers! 干杯!

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

相关问题 从 32 位 Windows 服务使用 64 位进程外 COM DLL - Using 64-bit out of process COM DLL from 32-bit Windows Serivce 使用NUnit在64位Windows上测试32位汇编 - Test 32-bit assembly on a 64 bit windows with NUnit 在32位进程下运行的GhostscriptLibraryNotInstalledException需要本机库 - GhostscriptLibraryNotInstalledException running under 32-bit process requires native library Windows Phone SDK在8.1 32位中的安装 - Windows phone sdk installation in 8.1 32-bit 在Windows 7 Pro 32位中生成.tlb文件 - Generation of .tlb Files in Windows 7 Pro 32-bit xapian问题 - 32位C#窗口 - xapian problems - 32-bit C# windows Windows 7上的32位应用程序的Environment.SpecialFolder.ProgramFiles值? - Environment.SpecialFolder.ProgramFiles value for a 32-bit application on Windows 7? 为什么OleDbConnection在64位进程上引发InvalidOperationException而在32位进程上引发OleDbException - Why OleDbConnection throws InvalidOperationException on 64-bit process and OleDbException on 32-bit process CLR /从32位进程切换到64位进程后的高内存消耗 - CLR / High memory consumption after switching from 32-bit process to 64-bit process 使用WMI,如何确定远程进程是32位还是64位? - Using WMI, how can I determine whether a remote process is 32-bit or 64-bit?
 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM