Stay organized with collections
Save and categorize content based on your preferences.
Issue: The pod fails to start the application and it is not
able to consume data mounted from the backup/recovery appliance.
This is happening due to the differences in the user ID
with which all the application processes ran on the
source machine—from where the data was captured—and
the one with which they are run on the Pod.
Solution: Explicitly set the security context for a pod and specify
the appropriate user ID value for runAsUser field in the
pod's YAML file. For example, if the MySQL application on
the source host ran all the processes with the user ID of 997,
then it is recommended to set the security context for the pod
to use the same user ID 997. This could be done by specifying
the following steps in the "spec" section of the Pod's YAML file.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-09-04 UTC."],[[["\u003cp\u003ePods may fail to start applications and consume mounted data due to discrepancies in user IDs between the source machine and the pod.\u003c/p\u003e\n"],["\u003cp\u003eThe primary cause of the issue is differing user IDs under which application processes run on the source and within the pod.\u003c/p\u003e\n"],["\u003cp\u003eTo resolve this, set the pod's security context explicitly, defining the correct user ID with the \u003ccode\u003erunAsUser\u003c/code\u003e field in the pod's YAML file.\u003c/p\u003e\n"],["\u003cp\u003eIt is recommended to align the \u003ccode\u003erunAsUser\u003c/code\u003e value in the pod's security context with the user ID used by application processes on the source machine.\u003c/p\u003e\n"]]],[],null,["# Troubleshoot container issues\n\n**Issue** : The pod fails to start the application and it is not\nable to consume data mounted from the backup/recovery appliance.\nThis is happening due to the differences in the `user ID`\nwith which all the application processes ran on the\nsource machine---from where the data was captured---and\nthe one with which they are run on the Pod.\n\n**Solution** : Explicitly set the security context for a pod and specify\nthe appropriate user ID value for **runAsUser** field in the\npod's YAML file. For example, if the MySQL application on\nthe source host ran all the processes with the user ID of 997,\nthen it is recommended to set the security context for the pod\nto use the same user ID 997. This could be done by specifying\nthe following steps in the \"spec\" section of the Pod's YAML file.\n\nSee [Configure a Security Context for a Pod or Container](https://kubernetes.io/docs/tasks/configure-pod-container/security-context/#set-the-security-context-for-a-pod)\nfor more information."]]
