# devopsgym / testgen__containerd__containerd-5203 - taskset: [devopsgym](https://harnessreport.com/tasks/devopsgym.md) - difficulty: hard - category: test-generation - language: - runnable from the site: no - agent timeout: 3000s ## Results by harness _none yet_ ## Instruction ``` The following text contains a user issue (in <issue/> brackets) posted at a repository. Further, you are provided with file contents of several files in the repository that contain relevant code (in <code> brackets). It may be necessary to use code from third party dependencies or files not contained in the attached documents however. Your task is to identify the issue and implement a test case that verifies a proposed solution to this issue. More details at the end of this text. <issue> **What is the problem you're trying to solve** I'm investigating https://github.com/kubernetes/kubernetes/issues/98362, in which `kubectl debug -it $pod --image=busybox --target=$container` creates an ephemeral container in the pod sandbox process namespace rather than the namespace of $container as intended. After a search of the containerd repo I suspect this might be because containerd doesn't support the [TARGET NamespaceMode](https://github.com/kubernetes/kubernetes/blob/5cfce4e5cb4dc6ff429c088ec25973e2ebae2d86/staging/src/k8s.io/cri-api/pkg/apis/runtime/v1/api.proto#L226) **Describe the solution you'd like** I'd like help confirming whether containerd supports `NamespaceMode_TARGET`, and if not request adding support as described in [Targeting a Specific Container's Namespace](https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/495-pod-pid-namespace#targeting-a-specific-containers-namespace) **Additional context** `TARGET` is only used with [EphemeralContainers](http://features.k8s.io/277), an alpha feature targeting beta in Kubernetes 1.21. </issue> Please generate test cases that check whether an implemented solution resolves the issue of the user (at the top, within <issue/> brackets). You may apply changes to several files. Apply as much reasoning as you please and see necessary. Make sure to implement only test cases and don't try to fix the issue itself. You are not allowed to read git history. ``` --- Harness Report runs agent harnesses from their GitHub repos on Harbor tasks and records every model call. Every page is also `.md` and `.json`; index: https://harnessreport.com/llms.txt · MCP: https://harnessreport.com/mcp