[SOLVED] Podman and something infernal around cgroupv2

This forum is dedicated to basic help and support :

Ask here your questions about basic installation and usage of Mageia. For example you may post here all your questions about getting Mageia isos and installing it, configuring your printer, using your word processor etc.

Try to ask your questions in the right sub-forum with as much details as you can gather. the more precise the question will be, the more likely you are to get a useful answer

[SOLVED] Podman and something infernal around cgroupv2

Postby Bronto » Mar 23rd, '21, 10:18

I have new Mageia 8 installation. And the first surprise for me was that I can not use docker anymore.. Red hat family switched to podman.. Ok. I installed podman and podman-docker translator.
I created 2 containers. One is postgres 9.6 and another - pgadmin4. And after restart system some warnings appeared in konsole as reply to each docker commad. Such as
Code: Select all
docker ps

And I see:
Code: Select all
WARN[0000] The cgroupv2 manager is set to systemd but there is no systemd user session available
WARN[0000] For using systemd, you may need to login using an user session
WARN[0000] Alternatively, you can enable lingering with: `loginctl enable-linger 1000` (possibly as root)
WARN[0000] Falling back to --cgroup-manager=cgroupfs   
WARN[0000] The cgroupv2 manager is set to systemd but there is no systemd user session available
WARN[0000] For using systemd, you may need to login using an user session
WARN[0000] Alternatively, you can enable lingering with: `loginctl enable-linger 1000` (possibly as root)
WARN[0000] Falling back to --cgroup-manager=cgroupfs   
WARN[0000] Failed to add conmon to cgroupfs sandbox cgroup: error creating cgroup path /libpod_parent/conmon: open /sys/fs/cgroup/cgroup.subtree_control: permission denied

Ok.. May be I just should not pay attention.. But each
Code: Select all
docker exec ...

fails with the same list of warnings + this one:
Code: Select all
WARN[0000] Error resizing exec session 029c2627e70296ff3ea282ddc9f3dbbe1c7456b054eea30856850fe01418a57a: could not open ctl file for terminal resize for container fdd57bbf20b28d488307e981b9b2c31279a0c9aa5b5e62a77236906fa8276e2e: open /home/<my_user_name>/.local/share/containers/storage/vfs-containers/fdd57bbf20b28d488307e981b9b2c31279a0c9aa5b5e62a77236906fa8276e2e/userdata/029c2627e70296ff3ea282ddc9f3dbbe1c7456b054eea30856850fe01418a57a/ctl: no such device or address

And now I am disappointed. What all this stuff around cgroupv2 is about? And what should I do from this point? Search for some other alternative to podman/docker? Hack my Mageia 8 installation with some cgroupv2_repair scripts? Switch back to Mageia 7?
Last edited by Bronto on Jun 30th, '21, 09:24, edited 1 time in total.
Bronto
 
Posts: 13
Joined: Mar 2nd, '17, 18:18

Re: Podman and something infernal around cgroupv2

Postby doktor5000 » Mar 24th, '21, 00:20

For the cgroupv2 issue, have a look at https://bugs.mageia.org/show_bug.cgi?id=27251
If you don't want to update docker yourself to something > 20.10 then you probably need the kernel boot option systemd.unified_cgroup_hierarchy=0

For some context information, have a look at e.g. https://medium.com/nttlabs/cgroup-v2-596d035be4d7 or https://chrisdown.name/talks/cgroupv2/c ... fosdem.pdf
Cauldron is not for the faint of heart!
Caution: Hot, bubbling magic inside. May explode or cook your kittens!
----
Disclaimer: Beware of allergic reactions in answer to unconstructive complaint-type posts
User avatar
doktor5000
 
Posts: 16720
Joined: Jun 4th, '11, 10:10
Location: Leipzig, Germany

Re: Podman and something infernal around cgroupv2

Postby Bronto » Mar 24th, '21, 08:55

doktor5000 wrote:If you don't want to update docker yourself to something > 20.10...

You say it like someone offered me to install docker 20.10 and I rejected:)) I see "docker 19" in Mageia control center.. And I made probe of it.. And there were the same otherworldly "cgroup" problems..
Do you mean that installing docker 20.10 instead of docker 19 solves problem? Actually I can find docker-ce-20 here: https://download.docker.com/linux/centos/7/x86_64/stable/Packages/.. Should it fit?
Bronto
 
Posts: 13
Joined: Mar 2nd, '17, 18:18

Re: Podman and something infernal around cgroupv2

Postby doktor5000 » Mar 24th, '21, 18:55

Sorry, I don't use docker on my own box, so I don't know. You would have to try that out yourself.
Cauldron is not for the faint of heart!
Caution: Hot, bubbling magic inside. May explode or cook your kittens!
----
Disclaimer: Beware of allergic reactions in answer to unconstructive complaint-type posts
User avatar
doktor5000
 
Posts: 16720
Joined: Jun 4th, '11, 10:10
Location: Leipzig, Germany

Re: Podman and something infernal around cgroupv2

Postby morgano » Mar 26th, '21, 12:17

Mandriva since 2006, then Mageia since 2011 at home & work. Thinkpad T43 & T400, Dell M4400, Acer Aspire 7. Workstation using LVM, LUKS, VirtualBox, BOINC
morgano
 
Posts: 793
Joined: Jun 15th, '11, 17:51
Location: Kivik, Sweden

Re: Podman and something infernal around cgroupv2

Postby Bronto » Mar 28th, '21, 13:56

Thanks to all of you!
Now I understand the problem better. And I have some ideas what to try..
Actually I made a try to install docker-ce-20.10.5-3.el7.x86_64.rpm... I downloaded it from centos repository. But.. It requires few other packages which are not present in my Mageia8 installation. May be I could try to satisfy this dependencies.. But may be I just should wait for docker 20 in mageia repository. As morgano says it's coming..
Bronto
 
Posts: 13
Joined: Mar 2nd, '17, 18:18

Re: Podman and something infernal around cgroupv2

Postby doktor5000 » Mar 28th, '21, 15:00

You could help test the update candidate, new docker 20.10 should already be available via core/updates_testing repository ofr mga8, you can install it as root like this:

Code: Select all
urpmi.update "Updates Testing"
urpmi docker --searchmedia=testing
Cauldron is not for the faint of heart!
Caution: Hot, bubbling magic inside. May explode or cook your kittens!
----
Disclaimer: Beware of allergic reactions in answer to unconstructive complaint-type posts
User avatar
doktor5000
 
Posts: 16720
Joined: Jun 4th, '11, 10:10
Location: Leipzig, Germany

Re: Podman and something infernal around cgroupv2

Postby Bronto » Mar 30th, '21, 13:14

I installed docker-20 from test repo.
Seems like it has some problems. I created pgadmin4 container:
Code: Select all
docker run --name pgadmin4 -p 5050:80 -e PGADMIN_DEFAULT_EMAIL={my_maile} -e PGADMIN_DEFAULT_PASSWORD={my_password} -d dpage/pgadmin4

And open in browser "localhost:5050". But browser does not open it.. I suppose something on dockers network level..
Where should I report about it?
Bronto
 
Posts: 13
Joined: Mar 2nd, '17, 18:18

Re: Podman and something infernal around cgroupv2

Postby morgano » Mar 31st, '21, 16:30

Thanks for testing!

Bronto wrote:Where should I report about it?


First, report like you have tested here above on that same bug in progress - because it may be a regression, and also because there should also be other people there knowing and testing docker.
Mandriva since 2006, then Mageia since 2011 at home & work. Thinkpad T43 & T400, Dell M4400, Acer Aspire 7. Workstation using LVM, LUKS, VirtualBox, BOINC
morgano
 
Posts: 793
Joined: Jun 15th, '11, 17:51
Location: Kivik, Sweden

Re: Podman and something infernal around cgroupv2

Postby Bronto » Mar 31st, '21, 17:00

morgano wrote:First, report like you have tested here above on that same bug in progress - because it may be a regression

Sorry.. This sentence is too complex for my non-native english.. What is "that same bug in progress" you talking about?
Bronto
 
Posts: 13
Joined: Mar 2nd, '17, 18:18

Re: Podman and something infernal around cgroupv2

Postby doktor5000 » Mar 31st, '21, 18:10

https://bugs.mageia.org/show_bug.cgi?id=27251 - which is for the update to docker 20.10
Cauldron is not for the faint of heart!
Caution: Hot, bubbling magic inside. May explode or cook your kittens!
----
Disclaimer: Beware of allergic reactions in answer to unconstructive complaint-type posts
User avatar
doktor5000
 
Posts: 16720
Joined: Jun 4th, '11, 10:10
Location: Leipzig, Germany

Re: Podman and something infernal around cgroupv2

Postby Bronto » May 8th, '21, 12:36

There is no any bright answer about docker 20.10... So could you please instruct me how to update Mageya kernel with "systemd.unified_cgroup_hierarchy=0"? There are some report that it will solve problem. But I absolutely don't know how to set systemd.unified_cgroup_hierarchy=0 to my Mageia kernel.. Googling with request "mageya how to set systemd.unified_cgroup_hierarchy=0" did not give me any Mageia related instructions...
Bronto
 
Posts: 13
Joined: Mar 2nd, '17, 18:18

Re: Podman and something infernal around cgroupv2

Postby doktor5000 » May 8th, '21, 19:29

There's no Mageia-related instructions necessary, you just need to add this as a kernel option, which is passed over by the bootloader (should be grub2 by default)
Have a look at https://wiki.mageia.org/en/How_to_set_u ... el_options
Cauldron is not for the faint of heart!
Caution: Hot, bubbling magic inside. May explode or cook your kittens!
----
Disclaimer: Beware of allergic reactions in answer to unconstructive complaint-type posts
User avatar
doktor5000
 
Posts: 16720
Joined: Jun 4th, '11, 10:10
Location: Leipzig, Germany

Re: Podman and something infernal around cgroupv2

Postby Bronto » May 17th, '21, 09:17

Thanks for instructions for setting kernel option. I set "systemd.unified_cgroup_hierarchy=0" option. Removed testing docker version (20.10) and installed docker 19 from default repository. Docker looks like working ok. But still all docker containers are not available from outside!
Ok.. May be problem is docker. I uninstalled docker and installed podman.. And... Absolutely the same situation! Docker containers are not available!!
Bronto
 
Posts: 13
Joined: Mar 2nd, '17, 18:18

Re: Podman and something infernal around cgroupv2

Postby Bronto » Jun 21st, '21, 09:51

I'm sorry for my last message about docker containers being not available.. Now I found that I need to add my user to docker group.. And I should work with docker from non root user. And in this case no more problems with containers not available on configured ports..
Looks like I reached suitable environment. I have Mageia 8 with kernel option "systemd.unified_cgroup_hierarchy=0".. And podman with podman-docker emalator plugin. And my user added to docker group. And looks like everything ok now. I don't want to say that podman is only one option. It's just last package which was installed after all my experiments and finally I found the solvation with non-root user..
Bronto
 
Posts: 13
Joined: Mar 2nd, '17, 18:18

Re: Podman and something infernal around cgroupv2

Postby doktor5000 » Jun 21st, '21, 13:58

Thanks for the feedback.

Please don't forget to mark the thread as solved, by editing the subject of the first post and prefix it with [SOLVED], thanks in advance.
Cauldron is not for the faint of heart!
Caution: Hot, bubbling magic inside. May explode or cook your kittens!
----
Disclaimer: Beware of allergic reactions in answer to unconstructive complaint-type posts
User avatar
doktor5000
 
Posts: 16720
Joined: Jun 4th, '11, 10:10
Location: Leipzig, Germany


Return to Basic support

Who is online

Users browsing this forum: No registered users and 1 guest