I haven’t noticed the path format when I created tarball, this time the format issue plays as a major blocker.
We use a module tar file to deploy Zen
in ICP4D cluster, when I use my customized tar file, I get:
1 | Loading images |
Let’s highlight the command:
1 | Running command: /xxx/InstallPackage/components/dpctl --config /xxx/InstallPackage/components/install.yaml helm rewriteChart -i /xxx/InstallPackage/modules/./xxx-iisee-zen:1.0.0//charts/*.tgz -o /xxx/InstallPackage/modules/./xxx-iisee-zen:1.0.0//charts/updated_xxx-iisee-zen100.tgz |
Look carefully there is a ./
in path /xxx/InstallPackage/modules/./xxx-iisee-zen:1.0.0/....
, this is because I create tarball use:
1 | tar cf xxx-iisee-zen-1.0.0.tar ./xxx-iisee-zen:1.0.0 |
the ./
will be put in the extract path! which is the trouble maker.
Correct way:
1 | cd <xxx-iisee-zen:1.0.0 parent folder> |
If we list the tarball contents, no prefix in the file structure:
1 | tar tvf xxx-iisee-zen-1.0.0.tar |
For more information about tar commands, I have a blob about it already <<Tar Command Daily Work Summary>>