AKS instance epp-aks-btat2 is running a specific container and exiting with 132, where Docker Desktop and other experiements run normally

Mushahid Mujtaba Mohammed 0

Xenia-MSFT 3,140 Reputation points Microsoft Vendor

2024-12-17T01:22:51.57+00:00

@Mushahid Mujtaba Mohammed Thanks for posting in our Q&A.

For this issue, it seems more related to Azure Kubernetes Service. So, I will add "Azure Kubernetes Service" tag. Let's wait for the related support engineer involve in this issue.

Thanks for your understanding.
Mounika Reddy Anumandla 1,300 Reputation points Microsoft Vendor

2024-12-17T03:43:41.6033333+00:00
Hi Mushahid Mujtaba Mohammed,

Welcome to the Microsoft Q&A Platform! Thank you for asking your question here.

The container runs fine on Docker Desktop and other environments, which implies the image and application are working as expected in those environments.

The AKS node where the container is running might lack support for certain CPU instructions (e.g., AVX, SSE4.2, etc.) that the application requires.

Common scenarios include:

Local machine CPU (e.g., your laptop) has a more modern architecture, supporting instructions like AVX or AVX2.

AKS nodes use Azure VMs that may have older or less capable CPUs without these instructions.

When your container attempts to execute these unsupported instructions, the process crashes with an illegal instruction error, which translates to exit code 132.

Troubleshooting steps:

Check Logs: Use kubectl logs to view the container logs

Look for any abnormal events in the Events section: Rebuild the Image for Compatibility: Ensure the image is built with a target architecture compatible with the AKS node's hardware.

Update or recreate the node pool with newer VM sizes. The node pool in AKS may be using older VM sizes that lack modern CPU capabilities.

If you have any further queries, do let us know.

If the comment is helpful, please click "upvote".
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Mounika Reddy Anumandla 1,300 Reputation points Microsoft Vendor

2024-12-19T03:41:26.0633333+00:00

Hi Mushahid Mujtaba Mohammed,

I hope you're doing well! Just following up to see if you’ve had an opportunity to review my last response.

Thank you!

If you have any further queries, do let us know.

If the comment is helpful, please click "upvote".
Nikhil Duserla 3,645 Reputation points Microsoft Vendor

2024-12-20T15:15:23.2066667+00:00

Hi Mushahid Mujtaba Mohammed,

I just wanted to follow up and see if you’ve had a chance to review last response provided by Mounika. If the answer is helpful, please click "Accept Answer" and "Upvote it."
Mushahid Mujtaba Mohammed 0 Reputation points

2024-12-20T15:27:43.7433333+00:00

Thanks Nikhil for your answer. Found the root cause of the issue. In our AKS environment we had installed One Agent whose libraries messed up with openjdk temurin17-binaries. Fixed by unsetting LD_PRELOAD through bash command and executed entry point.
Nikhil Duserla 3,645 Reputation points Microsoft Vendor

2024-12-23T13:35:06.43+00:00

Hi @Mushahid Mujtaba Mohammed,

Good catch! Glad the issue is resolved for you finally. I will have this answer promoted by reposting it. As an Original Poster(You) will not be able to accept your own answer. This is in the attempt to help others looking for a solution for a similar issue.

Thanks again for sharing the solution here. Have a good day!

1 answer

Nikhil Duserla 3,645 Reputation points Microsoft Vendor

2024-12-23T13:43:44.4433333+00:00

Hi @Mushahid Mujtaba Mohammed,

Welcome to the Microsoft Q&A Platform! Thank you for asking your question here.

Issue: AKS instance epp-aks-btat2 is running a specific container and exiting with 132, where Docker Desktop and other experiements run normally?

Solution: Issue was fixed by unsetting LD_PRELOAD with a bash command and subsequently executing the entry point.

This is in the attempt to help others looking for a solution for a similar issue. Please click "Accept Answer" and "Upvote it."
Please sign in to rate this answer.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

AKS instance epp-aks-btat2 is running a specific container and exiting with 132, where Docker Desktop and other experiements run normally

1 answer

Your answer