AKS version needs to match UID and GID with baremetal
Environment
http://10.239.235.18:8010/esp/files/Login.html
Description
Due to different UID and GID from the baremetal systems the pod is having issues accessing existing data on a share volume, we edited the _helper.tpl file to change the runAs... parameters, but the UID in /etc/passwd still point to 10000:10001 instead of 999:1001
I have no name!@roxie-agent-1-78584bd559-h8dbp:/$ grep hpcc /etc/passwd
That is what I would expect to see in a system configured as yours is. It will not prevent you from reading remote files owned by 999/1000.
If you have some volumes with data created by bare metal 999/1000 and some volumes with data created by AKS 10000/10001 then the workaround is only going to let you read one or the other, so a chmod is going to be required on set before you can proceed.
Fixed
Pinned fields
Click on the next to a field label to start pinning.
Due to different UID and GID from the baremetal systems the pod is having issues accessing existing data on a share volume, we edited the _helper.tpl file to change the runAs... parameters, but the UID in /etc/passwd still point to 10000:10001 instead of 999:1001
I have no name!@roxie-agent-1-78584bd559-h8dbp:/$ grep hpcc /etc/passwd
hpcc:x:10000:10001:hpcc runtime User:/home/hpcc:/bin/bash