Fresh install Docker cgroup mountpoint does not exist

Was facing this too so it might be useful
Downsides of disabling cgroups v2? Wasnt that needed for memavaild?

4 Likes

yes its needed by memavaild
thats why we enable it by default

6 Likes

I started to use Garuda KDE Dr460nized this Tuesday thanks to DistroTube and looking forward to document my issues after the migration from Manjaro.

It's also awesome to see such responsiveness from the community and devs.

and by the way thanks for this gorgeous distro which is also based on my all time favorite Arch Linux.

7 Likes

i think podman supports cgroup v2

6 Likes

you can install

sudo pacman -S podman-docker

and use it with

docker commands

5 Likes

Yes but No :smiley:

Since part of my job is development with docker I do not want to make another switch.
I remember 2-3 years ago when I started forcing my coworkers running projects in docker.
And yes it was literally force.

I was sick of 'But with my PHP/Apache/NGINX (place software X here) version it worked!'
Not to mention CI/CD and automated testing with docker. yada yada

I know that I could replace my local docker with podman, but I imagine some of my coworker will come to me with some docker problem and if I tell them 'Ohh I use podman now' they will strangle me right then and there.

But for another user which has no need to stick with a specific software this could be a good solution.

6 Likes

If you want to document things anyway, what about you write these directly to the wiki & link them here? :slight_smile: The wiki needs some love :grin:

I do like docker as well. Its not only that, the option to have reproducible setups and all config files in one directory is the selling point for me :smiley:

5 Likes

I am a little confused by this.
Is this the 'wiki' Garuda Linux FAQ ?

And also what is the workflow you propose here?
Write my solutions/problems as a comment to Garuda Linux FAQ ?

2 Likes
3 Likes

Ahh ok.
Yes I could do that. But I guess I have no permissions to do that :slight_smile:

2 Likes

Nice! :slight_smile: I pm'd you some information concerning that.
Thanks for participating!

4 Likes

All right, thanks for that.
I will add that to the wiki.

6 Likes

@BrutalBirdie

I am having the same issue, this solution didn't work for me.

I'm a linux noob so I figure I am doing something wrong?

cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a device; this may
# be used with UUID= as a more robust way to name devices that works even if
# disks are added and removed. See fstab(5).
#
# <file system>             <mount point>  <type>  <options>  <dump>  <pass>
UUID=70A3-BF56                            /boot/efi      vfat    umask=0077 0 2
UUID=c1fc10ac-4c60-4f06-a718-ce838e6d1146 /              btrfs   [email protected],defaults,noatime,space_cache,autodefrag,compress=zstd 0 1
UUID=c1fc10ac-4c60-4f06-a718-ce838e6d1146 /home          btrfs   [email protected],defaults,noatime,space_cache,autodefrag,compress=zstd 0 2
UUID=c1fc10ac-4c60-4f06-a718-ce838e6d1146 /root          btrfs   [email protected],defaults,noatime,space_cache,autodefrag,compress=zstd 0 2
UUID=c1fc10ac-4c60-4f06-a718-ce838e6d1146 /srv           btrfs   [email protected],defaults,noatime,space_cache,autodefrag,compress=zstd 0 2
UUID=c1fc10ac-4c60-4f06-a718-ce838e6d1146 /var/cache     btrfs   [email protected],defaults,noatime,space_cache,autodefrag,compress=zstd 0 2
UUID=c1fc10ac-4c60-4f06-a718-ce838e6d1146 /var/log       btrfs   [email protected],defaults,noatime,space_cache,autodefrag,compress=zstd 0 2
UUID=c1fc10ac-4c60-4f06-a718-ce838e6d1146 /var/tmp       btrfs   [email protected],defaults,noatime,space_cache,autodefrag,compress=zstd 0 2
UUID=c1ed9087-3378-4246-94ca-524fbf79a5f1 swap           swap    defaults,noatime 0 0
cgroup    /sys/fs/cgroup/systemd    cgroup    defaults

Did you reboot your system after that and did you run this?

sudo mkdir /sys/fs/cgroup/systemd

ps updated the fix again so the last part contains the mkdir part

4 Likes

Yep. but for some reason, when I reboot, the /sys/fs/cgroup/systemd directory no longer exists.

Not sure why.

1 Like

to be fair I did not even reboot since I did this :smiley:

Just tested the reboot and can confirm your claim.
The folder does so longer exist and does not get created on boot.

I will investigate.

1 Like

Was a solution ever found for this? I am having the same troubles

Docker 20.10 adds cgroups-v2 support which should make docker work without any workarounds :raised_hands:

6 Likes

Confirmed.

"But I use yay?!" fine..

yay -Syu docker-git --overwrite "*"