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

cri-dockerd sandbox diffing from kubadm sanbox #230

Closed
Toavina23 opened this issue Aug 30, 2023 · 3 comments
Closed

cri-dockerd sandbox diffing from kubadm sanbox #230

Toavina23 opened this issue Aug 30, 2023 · 3 comments

Comments

@Toavina23
Copy link

I am getting this error message when initializing my kubernetes cluster
detected that the sandbox image "registry.k8s.io/pause:3.6" of the container runtime is inconsistent with that used by kubeadm. It is recommended that using "registry.k8s.io/pause:3.9" as the CRI sandbox image

The initialization is complete and the cluster is operational but I am a bit worried about the risk of ignoring this warning message.

is there a fix to it ? I did not find a way to override the cri-dockerd sandbox version

@afbjorklund
Copy link
Contributor

Unfortunately the documentation is a bit confusing, it ended up under "Mirantis" header:

https://kubernetes.io/docs/setup/production-environment/container-runtimes/#docker

Overriding the sandbox (pause) image

The cri-dockerd adapter accepts a command line argument for specifying which container image to use as the Pod infrastructure container (“pause image”). The command line argument to use is --pod-infra-container-image.

@afbjorklund
Copy link
Contributor

It will be updated to use pause version 3.9 by default:

@Toavina23
Copy link
Author

Okay thanks for the informations.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants