Description of problem: I'm trying to debug issues in my OCP4 cluster (including tcpdump stuff) and while this works: ``` oc debug node/<node> chroot /host podman run -it --name rhel-tools --privileged \ --ipc=host --net=host --pid=host -e HOST=/host \ -e NAME=rhel-tools -e IMAGE=rhel7/rhel-tools \ -v /run:/run -v /var/log:/var/log \ -v /etc/localtime:/etc/localtime -v /:/host rhel7/rhel-tools ``` I'm wondering if there is a better way of doing this that doesn't seem so 'hacky'. It turns out oc debug allows you to specify a different image, but it just times out. Version-Release number of selected component (if applicable): 4.1 How reproducible: Try to `oc debug node` with a different image Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: I've tried in a regular OCP4 and crc environments.
Actually, the image is --image=rhel7/rhel-tools and it works: $ oc debug node/myhost.example.com --image=rhel7/rhel-tools Starting pod/myhostexamplecom-debug ... To use host binaries, run `chroot /host` Pod IP: 10.19.138.11 If you don't see a command prompt, try pressing enter. sh-4.2# sh-4.2# tcpdump --version tcpdump version 4.9.2 libpcap version 1.5.3 OpenSSL 1.0.2k-fips 26 Jan 2017 sh-4.2# exit Removing debug pod ... Closing the PEBKAC bugzilla, sorry for the noise.
*** This bug has been marked as a duplicate of bug 1728135 ***