We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When running the simulator in a docker or podman container - it would be great if we "just" could exec into that container and use kubectl directly.
For this it would be nice to have the kubectl binary in the image..
-> would that be possible to be added?
The text was updated successfully, but these errors were encountered:
Here is what I am doing:
mkdir /root/x
copy the supportbundle into that path and extract it
mkdir /root/x/sim
docker run -v /root/x/sim:/tmp/sim -v /root/x/supportbundle_31d93373-1ebd-4086-88bd-111d6b25c2da_2024-07-05T08-58-20Z/:/mnt -it rancher/support-bundle-kit:master-head /usr/bin/support-bundle-kit simulator --bundle-path=/mnt --sim-home /tmp/sim
then exit the container with ctrl-p / ctrl-q and do another docker exec -it <container> sh
docker exec -it <container> sh
Now it would be great if we could use kubectl directly in that container..
My workaround is to do a docker cp kubectl <container>:/ and use this - but if kubectl would be included already - it would be somewhat easier..
docker cp kubectl <container>:/
Sorry, something went wrong.
No branches or pull requests
When running the simulator in a docker or podman container - it would be great if we "just" could exec into that container and use kubectl directly.
For this it would be nice to have the kubectl binary in the image..
-> would that be possible to be added?
The text was updated successfully, but these errors were encountered: