Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Issues

Select view

Select search mode

 
1 of 1

AKS version needs to match UID and GID with baremetal

Fixed

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

hpcc:x:10000:10001:hpcc runtime User:/home/hpcc:/bin/bash

Conclusion

None
Pinned fields
Click on the next to a field label to start pinning.

Details

Components

Assignee

Reporter

Priority

Fix versions

Pull Request URL

https://github.com/hpcc-systems/HPCC-Platform/pull/15713

Affects versions

Created January 28, 2022 at 3:48 PM
Updated February 28, 2022 at 12:51 PM
Resolved February 2, 2022 at 4:22 PM

Activity

Show:

Richard Chapman January 28, 2022 at 5:50 PM

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.

Flag notifications