Closed AskAlice closed 1 year ago
@AskAlice thanks for creating this issue! Looks like the tar
command is not present in the target container, but it is required for the sync to function correctly. Could that be the case?
I am having the same issue
[fatal] start sync: start sync: error executing tar: : command terminated with exit code 126
tar
is available in the target container:
root@c8553b493b62:/go# tar --version
tar (GNU tar) 1.34
Copyright (C) 2021 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <https://gnu.org/licenses/gpl.html>.
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Written by John Gilmore and Jay Fenlason.
root@c8553b493b62:/go#
Maybe its a special version of it?
For me the issue was a Pod deployment with multiple containers without setting dev.sync.containerName=xxx
What happened?
running a docker image built with a custom script, that handles some aspect of tagging the image, it does pair up with the image but it then returns
What did you expect to happen instead?
sync to work
How can we reproduce the bug? (as minimally and precisely as possible)
Local Environment:
devspace --version
]devspace version 5.16.0
linux
kustomize
Kubernetes Cluster: minikube
Anything else we need to know?
/kind bug