Open fketelaars opened 8 months ago
I was going to raise the issue and saw this. @fketelaars thanks for proactively creating this. I will watch the situation. As a comment, the problem is more bigger then just ibm-pak part of the progress. It fails in many more components during the deployer progress and all related to similar flavor
I think I´m encountering the same issue on the step TASK [cp4ba-core : Extract installation repository]
with the following error message. I´m running the latest cloud-pak-deployer as a podman container on an intel mac.
"err": "/usr/bin/gtar: ibm-cp-automation/LICENSE: Cannot change ownership to uid 0, gid 0: Operation not permitted\n/usr/bin/gtar: ibm-cp-automation/README.md: Cannot change ownership to uid 0, gid 0: Operation not permitted\n/usr/bin/gtar: ibm-cp-automation/case.yaml: Cannot change ownership to uid 0, gid 0: Operation not permitted\n/usr/bin/gtar: ibm-cp-automation/certifications/files/ExternalSecurityReport.pdf: Cannot change ownership to uid 0, gid 0: Operation not permitted\n/usr/bin/gtar:
and so on
Running CPD on CentOS instead of macOS fixes the issue.
This might be related to the rootless podman in macbook installations. It can be solved by setting this env variable
export OLM_UTILS_LAUNCH_ARGS=" --platform linux/arm64 --userns=keep-id:uid=1001"
Note: platform parameter here is for M1 architecture
Describe the bug When installing the ibm-pak oc plugin on a Mac, the
unarchive
role fails because the tar.gz file has files owned by a non-existing user.Solution:
ibm-pak
no longer needs to be downloaded/installed as it is already in theolm-utils-v2
image.