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.

Sign up for GitHub

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

Jump to bottom

request: cgroup v2 CI infra (for testing Rootless Docker driver) #12456

Closed
AkihiroSuda opened this issue Sep 13, 2021 · 12 comments · Fixed by #15450
Closed

request: cgroup v2 CI infra (for testing Rootless Docker driver) #12456

AkihiroSuda opened this issue Sep 13, 2021 · 12 comments · Fixed by #15450
Assignees
@AkihiroSuda
Labels
area/testing kind/process Process oriented issues, like setting up CI priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.
Milestone
1.31.0

Comments

@AkihiroSuda
Copy link
Member

Support for Rootless Docker with cgroup v2 was merged in #12359 , but not tested on CI.

We need a cgroup v2 CI infra to test the rootless docker driver (and eventually rootless podman driver too).

cgroup v2 CI infra in other projects
@AkihiroSuda AkihiroSuda changed the title request: cgroup v2 CI infra request: cgroup v2 CI infra (for testing Rootless Docker driver) Sep 13, 2021
@afbjorklund
Copy link
Collaborator

@sharifelgamal ?

We talked about getting some Fedora infrastructure at some point or other (see #3552)

It's needed for testing other strange setups, such as btrfs and whatever next they come up with

@fkorotkov
Copy link

Hey there, Cirrus CI founder here. With Cirrus you can use a custom GCP VM image (it's free for OSS). For example, Podman is using a custom VM to test on Fedora. Just wanted to note these in case you'd prefer not to use Vagrant as a "middleman".

@AkihiroSuda
Copy link
Member Author

Hey there, Cirrus CI founder here. With Cirrus you can use a custom GCP VM image (it's free for OSS). For example, Podman is using a custom VM to test on Fedora. Just wanted to note these in case you'd prefer not to use Vagrant as a "middleman".

Is Fedora (not Fedora CoreOS) image publicly available?

@fkorotkov
Copy link

Is Fedora (not Fedora CoreOS) image publicly available?

They are not. The one publicly available are the CoreOS. Podman folks seems do build a regular Fedora though.

@sharifelgamal
Copy link
Collaborator

Adding testing infra for Fedora is on our near term list of things to do. I'll use this issue to track it.

@sharifelgamal sharifelgamal added area/testing kind/process Process oriented issues, like setting up CI priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. labels Sep 22, 2021
@sharifelgamal sharifelgamal added this to the 1.25.0-candidate milestone Sep 22, 2021
@sharifelgamal sharifelgamal self-assigned this Sep 22, 2021
@sharifelgamal sharifelgamal mentioned this issue Sep 22, 2021
Closed
@spowelljr spowelljr added priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. and removed priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. labels Nov 3, 2021
@sharifelgamal
Copy link
Collaborator

Update here, I ran our integration test suites on Ubuntu 21.10 with cgroupsv2 enabled, and we found a lot of general flakiness and instability.

With regards to Fedora, we have the ability to spin up Fedora machines on GCP, but they do not support nested virtualization, which makes them of limited use to us.

@medyagh medyagh modified the milestones: 1.25.0, 1.26.0-candidate Dec 13, 2021
@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue or PR as fresh with /remove-lifecycle stale
  • Mark this issue or PR as rotten with /lifecycle rotten
  • Close this issue or PR with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 13, 2022
@AkihiroSuda
Copy link
Member Author

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 14, 2022
@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue or PR as fresh with /remove-lifecycle stale
  • Mark this issue or PR as rotten with /lifecycle rotten
  • Close this issue or PR with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jun 12, 2022
@AkihiroSuda
Copy link
Member Author

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jun 12, 2022
@spowelljr spowelljr modified the milestones: 1.26.0, 1.27.0-candidate Jun 24, 2022
@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue or PR as fresh with /remove-lifecycle stale
  • Mark this issue or PR as rotten with /lifecycle rotten
  • Close this issue or PR with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 9, 2022
@RA489
Copy link

RA489 commented Oct 28, 2022

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 28, 2022
@spowelljr spowelljr modified the milestones: 1.27.0-previous, 1.29.0 Nov 28, 2022
@AkihiroSuda AkihiroSuda mentioned this issue Dec 2, 2022
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@AkihiroSuda AkihiroSuda

Labels
area/testing kind/process Process oriented issues, like setting up CI priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.
Projects
None yet
Milestone
1.31.0
Development

Successfully merging a pull request may close this issue.

CI: add functional_docker_rootless_containerd_ubuntu AkihiroSuda/minikube
9 participants
@fkorotkov @medyagh @AkihiroSuda @afbjorklund @k8s-ci-robot @sharifelgamal @RA489 @spowelljr @k8s-triage-robot