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

containerd integration: verify behavior when switching snapshotters #45273

Open
thaJeztah opened this issue Apr 5, 2023 · 0 comments
Open

containerd integration: verify behavior when switching snapshotters #45273

thaJeztah opened this issue Apr 5, 2023 · 0 comments
Labels
area/images containerd-integration Issues and PRs related to containerd integration kind/enhancement Enhancements are not bugs or new features but can improve usability or performance.

Comments

@thaJeztah
Copy link
Member

thaJeztah commented Apr 5, 2023

Description

While we currently do not provide an option to specify the snapshotter to use
for individual containers (we may want to add this option in future), currently
it already is possible to configure the snapshotter in the daemon configuration,
which could (likely) cause issues when changing and restarting the daemon.

  • image list: currently assumes that all images are using the same snapshotter
  • some code paths may assume that the snapshotter didn't change (but the container
    may have been created with the previous snapshotter)

Other parts to verify;

  • image save / load (if the intent is to use the loaded image for a container with a specific snapshotter)
  • "docker pull" currently uses the default snapshotter. If the "docker pull" is done implicitly as part of a "docker run", we may have to pass this information along.
  • "docker build" (both classic and BuildKit)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/images containerd-integration Issues and PRs related to containerd integration kind/enhancement Enhancements are not bugs or new features but can improve usability or performance.
Projects
None yet
Development

No branches or pull requests

1 participant