scratch-debugger: debugger fails to start if the /docker-cli directory does not exist
jeromefroe opened this issue · 5 comments
The scratch-debugger/debug.sh
script fails to work if the /docker-cli
directory does not exist because wget
is unable to download docker into it. For example:
$ ./debug.sh httpbin-7cb89bfd94-tk4j2
Debug Target Container:
Pod: httpbin-7cb89bfd94-tk4j2
Namespace: default
Node: ip-172-20-62-198.ec2.internal
Container: httpbin
Container ID: 64e9e36eee378541839bbfd66726b622b7234abe2a99af7d9d8d6d034529b859
Runtime: docker
"Installing busybox to /tmp/debug-tools ..."
...
+ wget -qO/docker-cli/docker.tgz https://download.docker.com/linux/static/stable/x86_64/docker-17.12.0-ce.tgz
wget: can't open '/docker-cli/docker.tgz': No such file or directory
pod "debugger-8gq6n" deleted
By adding a command to ensure docker-cli
exists prior to the wget
command I was able to get the container to start.
Is there any solution?
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close
.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten
.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close
.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten
Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen
.
Mark the issue as fresh with /remove-lifecycle rotten
.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close
@fejta-bot: Closing this issue.
In response to this:
Rotten issues close after 30d of inactivity.
Reopen the issue with/reopen
.
Mark the issue as fresh with/remove-lifecycle rotten
.Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.