-
Notifications
You must be signed in to change notification settings - Fork 67
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to troubleshoot why nanoserver is failing #564
Comments
Thank you for creating an Issue. Please note that GitHub is not an official channel for Microsoft support requests. To create an official support request, please open a ticket here. Microsoft and the GitHub Community strive to provide a best effort in answering questions and supporting Issues on GitHub. |
You can use something like https://learn.microsoft.com/en-us/sysinternals/downloads/procmon to identify the missing dll loads. You can run it on the host and will get the events from the container. |
@jsturtevant Thanks for the help. I was able to track CreateFile and LoadImage calls to identify what dlls were getting loaded. However, I'm now getting an error message like " ---> System.DllNotFoundException: Unable to load DLL 'somedll.dll' or one of its dependencies: The specified procedure could not be found. (0x8007007F)" From what I can tell in procmon, it tried to load ole32.dll a second time from the application folder and then loaded faultrep.dll (which I'm guessing means the application gave up) Are there other tools I can use to determine if there is a specific OS API function that's missing? |
I'm trying to migrate my application from server core base image to nano server base image to reduce the image size. However, the container just exists with exit code -1073741515 which seems to suggest some dependency is missing. Are there tools or error logs I can check to help troubleshoot?
The application based on dotnet core, but I think some of the package dependencies are written in C++, which is where I suspect needs additional dependencies.
The text was updated successfully, but these errors were encountered: