Skip to content
New issue

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

Support customizing containerd namespace #47957

Open
ttc0419 opened this issue Jun 12, 2024 · 3 comments
Open

Support customizing containerd namespace #47957

ttc0419 opened this issue Jun 12, 2024 · 3 comments
Labels
containerd-integration Issues and PRs related to containerd integration kind/feature Functionality or other elements that the project doesn't currently have. Features are new and shiny

Comments

@ttc0419
Copy link

ttc0419 commented Jun 12, 2024

Description

By default, docker engine uses moby containerd namespace, however other runtime like kubelet uses k8s.io and there's no way to change it. Please consider support customizing containerd namespace so users can have a unified workspace.

@ttc0419 ttc0419 added kind/feature Functionality or other elements that the project doesn't currently have. Features are new and shiny status/0-triage labels Jun 12, 2024
@thaJeztah thaJeztah added containerd-integration Issues and PRs related to containerd integration and removed status/0-triage labels Jun 12, 2024
@vvoland
Copy link
Contributor

vvoland commented Jun 12, 2024

There already is a daemon command line flag that allows to specify the containerd namespace to use:

$ dockerd --help

Usage:  dockerd [OPTIONS]

A self-sufficient runtime for containers.

Options:
...
      --containerd-namespace string           Containerd namespace to use (default "moby")

@ttc0419
Copy link
Author

ttc0419 commented Jun 12, 2024

@vvoland Thanks for the info, I can list images now but I still cannot list containers running using the docker ps command, what might be the reason?

I already added the following to the daemon.json:

{
  "features": {
    "containerd-snapshotter": true
  }
}

@vvoland
Copy link
Contributor

vvoland commented Jun 12, 2024

Right, it only affects the images as docker doesn't use the containerd as a source of truth for the containers, as it has its own containers db, so you won't be able to see any containers started outside of docker in docker ps.

I think we want to eventually use the containerd as a source of truth for containers too, but that's not a priority right now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
containerd-integration Issues and PRs related to containerd integration kind/feature Functionality or other elements that the project doesn't currently have. Features are new and shiny
Projects
None yet
Development

No branches or pull requests

3 participants