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

[Rancher2] Single Node Using Docker fails with cgroups v2 #46

Open
dgiebert opened this issue Aug 11, 2022 · 3 comments · May be fixed by rancher/docs#4251
Open

[Rancher2] Single Node Using Docker fails with cgroups v2 #46

dgiebert opened this issue Aug 11, 2022 · 3 comments · May be fixed by rancher/docs#4251
Labels
effort/3 good-first-issue
Milestone
Next

Comments

@dgiebert
Copy link
Contributor

Request Summary:

It seems to be a known issue that the single node docker install does not work on operating systems using the newer cgroups v2.
Therefore I would suggest adding a section to the installation page warning about that fact and pointing the users to a k3s + helm setup.

Maybe similar to how its done here: https://rancher.com/docs/rancher/v2.6/en/backups/restoring-rancher/#known-issues

Details:

Some example issues from rancher/rancher
@dgiebert dgiebert linked a pull request Aug 11, 2022 that will close this issue
Open
@btat btat transferred this issue from rancher/docs Sep 13, 2022
@lerminou
Copy link

Hi, I found this doc bug but I also have the prerequisite fix when using cgroupv2, which kernel module to enable and more
we also fix the entrypoint rancher container

see: rancher/rancher#36238 (comment)

@github-actions
Copy link
Contributor

This repository uses an automated workflow to automatically label issues which have not had any activity (commit/comment/label) for 90 days. This helps us manage the community issues better. If the issue is still relevant, please add a comment to the issue so the workflow can remove the label and we know it is still valid. If it is no longer relevant (or possibly fixed in the latest release), the workflow will automatically close the issue in 30 days. Thank you for your contributions.

@IceCodeNew
Copy link

IceCodeNew commented Dec 14, 2022 •
edited
Loading

I am interested in this issue, please do not close it.

@btat btat removed the status/stale label Dec 21, 2022
@btat btat added this to the Next milestone Mar 1, 2023
@github-actions github-actions bot mentioned this issue May 22, 2023
Closed
@btat btat added the effort/3 label Dec 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
effort/3 good-first-issue
Projects
None yet
Milestone
Next
Development

Successfully merging a pull request may close this issue.

Added warning for cgroups to single node docker dgiebert/docs
4 participants
@btat @lerminou @dgiebert @IceCodeNew