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

Container runtime alternatives to Docker #76

Closed
lwilson opened this issue May 11, 2020 · 11 comments
Closed

Container runtime alternatives to Docker #76

lwilson opened this issue May 11, 2020 · 11 comments
Labels
enhancement New feature or request stale This issue is in danger of being automatically closed
Milestone

Comments

@lwilson
Copy link
Contributor

lwilson commented May 11, 2020

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

@lwilson lwilson added the enhancement New feature or request label May 11, 2020
@lwilson lwilson added this to Wishlist in Future Features via automation May 11, 2020
@lwilson lwilson moved this from Wishlist to Will Implement in Future Features May 18, 2020
@lwilson
Copy link
Contributor Author

lwilson commented May 18, 2020

@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).

@j0hnL
Copy link
Collaborator

j0hnL commented May 18, 2020

it's worth moving away from Docker for lighter weight CRI-O environments. Let's give it a shot.

@j0hnL
Copy link
Collaborator

j0hnL commented May 18, 2020

attempted to swap docker with CRI-O but led to failures and unable to start multi node k8s with our current setup using k8s v1.16.7 with cri-o v1.16

  • coreDNS is not scheduled
  • need to edit default config to change cgroup from systemd to cgroupfs

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.

@j0hnL j0hnL closed this as completed May 18, 2020
Future Features automation moved this from Will Implement to Done May 18, 2020
@lwilson lwilson reopened this Oct 19, 2020
@lwilson
Copy link
Contributor Author

lwilson commented Oct 19, 2020

@j0hnL I'm re-opening this. I think we should reconsider use of CRI-O with either runc or possibly crun for the container runtime. This would help us with both the Intel FPGA enablement (#84), and get us using a lighter weight container runtime.

@lwilson lwilson moved this from Done to Wishlist in Future Features Oct 19, 2020
@j0hnL
Copy link
Collaborator

j0hnL commented Oct 20, 2020

CentOS8 has podman and buildah in default repos. We should explore using podman instead of docker.

@lwilson lwilson changed the title Switch from Docker to CRI-O Container runtime alternatives to Docker Oct 20, 2020
@lwilson
Copy link
Contributor Author

lwilson commented Oct 20, 2020

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 podman for it to work with Kubernetes, correct?

Also, since we are already considering moving to CentOS8 (#106) for OpenHPC (#37) this would be good to resolve.

@j0hnL
Copy link
Collaborator

j0hnL commented Oct 20, 2020

We should consider the following limitations when running rootless containers:

https://github.com/containers/podman/blob/master/rootless.md

@stale
Copy link

stale bot commented Apr 29, 2021

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.

@stale stale bot added the stale This issue is in danger of being automatically closed label Apr 29, 2021
@j0hnL j0hnL added this to the v1.1.0 milestone Apr 29, 2021
@stale stale bot removed the stale This issue is in danger of being automatically closed label Apr 29, 2021
@j0hnL
Copy link
Collaborator

j0hnL commented Apr 29, 2021

the team is currently reviewing containerd and cri-o for 1.1 release

@lwilson
Copy link
Contributor Author

lwilson commented May 11, 2021

We are currently discussion CRI-O vs containerd in discussion #332.

@stale
Copy link

stale bot commented Jul 10, 2021

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.

@stale stale bot added the stale This issue is in danger of being automatically closed label Jul 10, 2021
@stale stale bot closed this as completed Jul 24, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request stale This issue is in danger of being automatically closed
Projects
No open projects
Future Features
  
Wishlist
Development

No branches or pull requests

2 participants