kubectl copying and transfering file to a pod without tar installed

In general we would have tar installed on a kubernetes pod. Sometimes when things are not happening, we can still copy to the container using the following command :- 

Copy to container


cat local-backup.tar.gz | kubectl exec -i -n cattle-resources-system \
rancher-backup-57c997f8cd-fxlb4 -c rancher-backup -- \
sh -c 'cat > /var/lib/backups/backup.tar.gz'

Copying from container 


kubectl exec -n cattle-resources-system rancher-backup-84576c498c-lpjh2 \
-c rancher-backup -- cat /var/lib/backups/default-location-recurring-backup-8723b2bd-e272-430e-89f6-14a133f8a417-2026-02-25T03-12-05Z.tar.gz \
> local-backup.tar.gz




Comments

Post a Comment

Popular posts from this blog

vllm : Failed to infer device type

Trying to run vllm without gpu will typicaly lands you into this issue. To resolve this issue: we can use set these both. Setting one does not work for me. So i had to configure both settings below:- 1.  environment variable CUDA_VISIBLE_DEVICES = "" 2. in the command line, change to use device cpu and remove  tensor-parallel-size. For example, python3 -m vllm.entrypoints.openai.api_server --port 8080 --model deepseek-ai/DeepSeek-R1 --device cpu --trust-remote-code --max-model-len 4096" References https://docs.vllm.ai/en/latest/getting_started/troubleshooting.html#failed-to-infer-device-type
Read more

android studio kotlin source is null error

Image
This org.jetbrains.kotlin.util.FileAnalysisException with a java.lang.IllegalArgumentException: source must not be null is a known issue that can sometimes occur with the Kotlin compiler. It seems to be related to how the compiler analyzes certain source code structures. When this happens, you need to go clean your project and do another rebuild.  For my case, I was trying to test out the databinding = true feature. 
Read more

NodeJS: Error: spawn EINVAL in window for node version 20.20 and 18.20

Encounter this issue when running autorest (that uses nodejs).  I am using node version:  v18.20.2 After i revert to use node v18.12.0, then i was able to get my app to run without this error. Since i am working with Azure devops yaml, i was able to use the following to resolve my issue.  - task : NodeTool@0   inputs :     versionSource : 'spec'     versionSpec : '18.18.0'
Read more