You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on May 28, 2021. It is now read-only.
Kubernetes version (use kubectl version): v1.10.3+coreos.0
Cloud provider or hardware configuration: In house on metal (coreos on CISCO HW)
OS (e.g. from /etc/os-release): Container Linux by CoreOS 1688.5.3 (Rhyolite)
Kernel (e.g. uname -a): Linux dsp-ops3 4.14.32-coreos Allow user to create a my.cnf configuration file #1 SMP Tue Apr 3 05:21:26 UTC 2018 x86_64 Intel(R) Xeon(R) CPU E5-2680 v4 @ 2.40GHz GenuineIntel GNU/Linux
Others:
What happened?
kubectl cp fails with exit code 126 (as tar is missing from the images).
What you expected to happen?
kubectl cp works.
How to reproduce it (as minimally and precisely as possible)?
kubectl -n artifactory cp ./downloads/mysqldump.sql artifactory-mysql-0:/tmp/ -c mysql
OCI runtime exec failed: exec failed: container_linux.go:348: starting container process caused "exec: \"tar\": executable file not found in $PATH": unknown
command terminated with exit code 126
Anything else we need to know?
Would be nice to be able to restore backups that haven't been created with the operator e.g. "live" data or investigate mysql directly using debug tools etc.