Docker container killed only when executing in Eclipse: Error Code 137

[dsecca-mss]

Hello,

My organization uses a Docker image and launches a container within Eclipse to compile an application within the IDE. When this Docker container executes in Eclipse, the container halts during the project's compilation with Error Code 137. This error does not occur when we launch the Docker image and container outside of Eclipse (i.e we can compile the project outside of Eclipse with no issues).

This was observed with the following environment:

Docker Desktop v4.44.1 using WSL2 v2.5.10.0.

Eclipse 2024-12 (4.34.0)

C/C++ Docker Container Launch Support v11.6.1.202406241230

Docker Tooling v5.17.0.202411262017

We have used previous versions of Eclipse and Docker Tooling and we have never encountered this issue before.

We have ruled out the following:

1. Corruption/Issue with the Docker image. We have tried rebuilding the Docker image and this does not resolve the issue.
2. CPU and RAM usage of the Docker image/container were monitored during the container's execution and there was no excessive usage.
3. Eclipse's RAM and CPU usage were monitored during compilation; RAM usage did not exceed its normal operating usage. Same for the CPU usage.
4. Looking into Eclipse's C/C++ Build configurations, there is no evidence of the Docker image being launched with limited RAM or CPU restrictions which could potentially starve the container and force it to be killed.
5. From the Docker logs, we noticed that a kill signal was sent to the Docker Daemon to terminate the container, however it's not clear what the root cause is from the logs.

Could this be a bug within the Docker Tooling logic and some issue with the interface to Docker?

Let me know if you need any additional information.

Thanks,
David

[akurtakov]

Ideally an image and project to reproduce the issue. Rigth now , it is questionable whether anyone can reproduce the problem without investing huge amount of time .

[dsecca-mss]

Hello @akurtakov,

Thanks for your prompt response. I'm not sure if I can provide the exact project and Docker image since there is some proprietary information in them. I will check back and see what we can provide.

Thanks

[akurtakov]

The exact project is not needed, it is actually better to get as simple as possible project+image that reproduces the issue.

[dsecca-mss]

Hi @akurtakov ,

Sorry for the late reply! I was able to reproduce the issue with two sample projects. One uses a Sleep delay and the other compiles some sample code and also uses a sleep delay to trigger the exit code. For some reason, the applications consistently fail to execute past 31 seconds.

May I send these files to you via the email in your Github profile? I can send them via our File Share system.

Thanks,
David

[akurtakov]

I would prefer if you share them on github so someone else might jump in as I'm quite busy and wouldn't be able to look into it soon.

[dsecca-mss]

Hi @akurtakov

I spoke to our IT personnel and we can provide a link to the sample projects and Docker image. If you may not be the one to investigate this issue, would it be possible to provide the name(s) and email(s) of anyone who will investigate? We cannot paste any open links as per our IT policy.

Thanks,
David