Code Monkey home page Code Monkey logo

Comments (18)

aylei avatar aylei commented on June 11, 2024 1

Sorry for the late response, it is caused by an unstable debug-agent pushed to docker hub recently. It should have been fixed now, please run the command again to verify.

Since kubectl-debug plugin will still pull debug-agent:latest by default before #135 get fixed, it is recommend to configure or specify --agent-image=aylei/debug-agent:${version} if you are using a stable version of the plugin.

from kubectl-debug.

lwabish avatar lwabish commented on June 11, 2024 1

@lwabish could you please try aylei/debug-agent:v0.1.1?

Just tried using kubectl debug ${POD_NAME} --agent-image=aylei/debug-agent:v0.1.1,worked as expected

from kubectl-debug.

lx1036 avatar lx1036 commented on June 11, 2024

me too. how to resolve it?

from kubectl-debug.

wanminny avatar wanminny commented on June 11, 2024

+1

from kubectl-debug.

ComeonBug avatar ComeonBug commented on June 11, 2024

+1

from kubectl-debug.

yaoyaoio avatar yaoyaoio commented on June 11, 2024

建议先docker pull nicolaka/netshoot:latest 一下看看

from kubectl-debug.

hillbun avatar hillbun commented on June 11, 2024

docker pull nicolaka/netshoot:latest可以

from kubectl-debug.

fforloff avatar fforloff commented on June 11, 2024

The same error for me. While pulling the image locally works, the "kubectl debug..." does not.

from kubectl-debug.

lwabish avatar lwabish commented on June 11, 2024

seems that we need to ensure the images exists on the cluster nodes

from kubectl-debug.

fforloff avatar fforloff commented on June 11, 2024

seems that we need to ensure the images exists on the cluster nodes

which was not the case before

from kubectl-debug.

lwabish avatar lwabish commented on June 11, 2024

seems that we need to ensure the images exists on the cluster nodes

which was not the case before

right, last time I didn't pre pull the netshoot image

from kubectl-debug.

lwabish avatar lwabish commented on June 11, 2024

Sorry for the late response, it is caused by an unstable debug-agent pushed to docker hub recently. It should have been fixed now, please run the command again to verify.

Since kubectl-debug plugin will still pull debug-agent:latest by default before #135 get fixed, it is recommend to configure or specify --agent-image=aylei/debug-agent:${version} if you are using a stable version of the plugin.

Thanks for your work. Tried again but still not fixed. I have reinstalled the debug-agent and also tried brew upgrade kubectl-debug. Is there anything else I forgot?

from kubectl-debug.

aylei avatar aylei commented on June 11, 2024

Thanks for your work. Tried again but still not fixed. I have reinstalled the debug-agent and also tried brew upgrade kubectl-debug. Is there anything else I forgot?

Are you encountering the same error (image not found)? And what's the image of debug agent?

from kubectl-debug.

lwabish avatar lwabish commented on June 11, 2024

Thanks for your work. Tried again but still not fixed. I have reinstalled the debug-agent and also tried brew upgrade kubectl-debug. Is there anything else I forgot?

Are you encountering the same error (image not found)? And what's the image of debug agent?

Yes.The debug-agent daemonset is using aylei/debug-agent:latest and the imagePullPolicy has been set to always.

from kubectl-debug.

aylei avatar aylei commented on June 11, 2024

@lwabish could you please try aylei/debug-agent:v0.1.1?

from kubectl-debug.

alexdoka avatar alexdoka commented on June 11, 2024

@lwabish it doesn't work for me

from kubectl-debug.

lwabish avatar lwabish commented on June 11, 2024

@lwabish it doesn't work for me

append --agentless=true

from kubectl-debug.

moluzhui avatar moluzhui commented on June 11, 2024

Hi I run into this problem using agent-less default configuration. However, I found it works if I set verbose to 1 Looks wired.

Waiting for pod debug-agent-pod-xxx to run...
Forwarding from 127.0.0.1:10027 -> 10027
Forwarding from [::1]:10027 -> 10027
Handling connection for 10027
                             Start deleting agent pod my-pod-xxx
error execute remote, Internal error occurred: error attaching to container: Error: No such image: nicolaka/netshoot:latest
error: Internal error occurred: error attaching to container: Error: No such image: nicolaka/netshoot:latest

@aylei @themez The problem seems to be caused here, I delete the verbosity comparison in this part, and then I can download the image

// pkg/agent/runtime.go
	// delete if statement
        if cfg.verbosity > 0 {
		term.DisplayJSONMessagesStream(out, cfg.stdout, 1, true, nil)
	}

I understand that I went to the follow-up process(creat container) before the image pull was completed, so it caused an error

But the docker client uses http, which seems to return resp.body directly, there is no delay waiting problem.

	out, err := c.client.ImagePull(ctx, image, types.ImagePullOptions{RegistryAuth: authStr})

Looking forward to solving the confuse.

make build by master branch

from kubectl-debug.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.