jpetazzo/pipework

Update for usage with cgroups v2?

sotiris-bos opened this issue · 5 comments

sotiris-bos commented

A recent update broke pipework for me.

I have to manually force the system to use cgroups v1 in order for it to work.

Is there any chance you can update pipework to work with cgroups v2?

This is still a very useful tool that is essential for some of us.

jpetazzo commented

Hi!

I don't plan to update pipework (it was meant to be a stopgap tool before Docker supported host networking and network plugins; which was... 6-ish years ago😅) but if someone creates a fork that supports cgroups v2, I will be more than happy to link it on the front page at the top of the README, to make sure other folks find it easily.

I'm curious, though, I wonder how folks do use pipework these days?

Thank you,

  • 👍1
sotiris-bos commented

I am using it to pass through SR-IOV interfaces to containers instead of exposing the host networking or running bridges.

That way I have containers with DHCP addresses from my router with their own, multi-gigabit capable interface.

Your repo did not work with SR-IOV interfaces though, some changes were needed to be made to the entrypoint script, with the help of dreamcat4 if I remember correctly.

gaby commented

I use it heavily for attaching containers to the OpenVSwitch bridge, without having to use docker network syntax, it's just way easier to do with pipework.

yoursunny commented

if someone creates a fork that supports cgroups v2, I will be more than happy to link it on the front page at the top of the README

There's a Pull Request supporting cgroups v2: #249
Can @jpetazzo merge it?

jpetazzo commented

Merged!

(Note: I'm not using pipework myself anymore, so I merged without testing; hoping that it will be useful to others :))