Skip to content

containerd integration: implement automatic snapshotter selection #44076

@thaJeztah

Description

@thaJeztah

Description

With Graphdrivers, the docker daemon automatically selects the most suitable (opinionated / configurable) storage driver to use by

  • checking what the previously used storage-driver was
  • trying each storage-driver, and if supported (based on backing filesystem, distro, etc) picks the first one
  • falling back to vfs as last resort

With the containerd integration we should have a similar selection to make things "work" out of the box. Currently, we use containerd.DefaultSnapshotter as a default, but this const is hard-coded;

We should:

  • Get a list of snapshotters supported by containerd (containerd checks if they can be loaded)
  • Pick the first one from the list, in an (opinionated) order.
  • Consider if we want (e.g.) aufs and/or devicemapper to be part of automatic selection, or only "manual"

Metadata

Metadata

Assignees

No one assigned

    Labels

    containerd-integrationIssues and PRs related to containerd integrationkind/featureFunctionality or other elements that the project doesn't currently have. Features are new and shiny

    Projects

    Status

    To do

    Status

    Optional

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions