-
Notifications
You must be signed in to change notification settings - Fork 107
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
Container runtime alternatives to Docker #76
Comments
@j0hnL should we go with CRI-O via CentOS, or use Fedora CoreOS (see #57)? My position is that we install via CentOS, as we're still using the host OS for bare-metal HPC via Slurm. It appears that there is already a CRI-O build in the CentOS7 repos (https://cbs.centos.org/koji/rpminfo?rpmID=167524). |
it's worth moving away from Docker for lighter weight CRI-O environments. Let's give it a shot. |
attempted to swap docker with CRI-O but led to failures and unable to start multi node k8s with our current setup using
I would like to revisit CRI-O with newer version but let's call it for v1.16 and stick with docker on CentOS7 for now. |
CentOS8 has |
I changed the title of this issue to reflect that we are considering multiple options as Docker alternatives. @j0hnL I believe we need CRI-O on top of Also, since we are already considering moving to CentOS8 (#106) for OpenHPC (#37) this would be good to resolve. |
We should consider the following limitations when running rootless containers: https://github.com/containers/podman/blob/master/rootless.md |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
the team is currently reviewing containerd and cri-o for 1.1 release |
We are currently discussion CRI-O vs containerd in discussion #332. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Is your feature request related to a problem? Please describe.
Switch the container runtime from Docker/containerd to CRI-O
Describe the solution you'd like
https://kubernetes.io/docs/setup/production-environment/container-runtimes/#cri-o
Describe alternatives you've considered
We could stick with Docker, but would probably need to move off of the CentOS repos and onto CE.
Additional context
N/A
The text was updated successfully, but these errors were encountered: