Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Masalah: Pod gagal memulai aplikasi dan tidak
dapat menggunakan data yang dipasang dari appliance pencadangan/pemulihan.
Hal ini terjadi karena perbedaan user ID
yang digunakan untuk menjalankan semua proses aplikasi di
mesin sumber—tempat data diambil—dan
yang digunakan untuk menjalankannya di Pod.
Solusi: Tetapkan konteks keamanan untuk pod secara eksplisit dan tentukan
nilai ID pengguna yang sesuai untuk kolom runAsUser di
file YAML pod. Misalnya, jika aplikasi MySQL di
host sumber menjalankan semua proses dengan ID pengguna 997,
sebaiknya tetapkan konteks keamanan untuk pod
agar menggunakan ID pengguna 997 yang sama. Hal ini dapat dilakukan dengan menentukan
langkah-langkah berikut di bagian "spec" pada file YAML Pod.
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Sulit dipahami","hardToUnderstand","thumb-down"],["Informasi atau kode contoh salah","incorrectInformationOrSampleCode","thumb-down"],["Informasi/contoh yang saya butuhkan tidak ada","missingTheInformationSamplesINeed","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 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."]]
