Thomas Weber

I found more debugging time and was able to test against liblxc1 3.0.4 from ubuntu eon. This version is not affected so i guess the backported cgroup handling from 3.0.4...

@joshiparth1000 thank you for your contribution! I will take a closer look within a few days. Maybe you can check PR #116 in the meantime to see if there is...

@joshiparth1000 : What about integrating your feature with the existing network_mode driver configuration option. It would build upon the ideas from #116, adding a network_mode=pod:somepod and network_mode=cni:first,second

@ahjohannessen please see also issue #71 You can certainly configure the authentication directly on your host. See documentation at https://github.com/containers/image/blob/main/docs/containers-auth.json.5.md It's for now not possible to manage this file directly...

@harningt i'd like to add a map of "logical name" => "/path/to/socket" to the driver options. Each task configuration would refer to such a socket name (think "root", "tenant-a", "tenant-b"...

@optiz0r thank you for the bug report and your analysis. We will have a look.

Well, this is a bit of a clash between nomad, podman and kubernetes concepts. Nomad has task groups instead of pods. A task group can be used to relate several...

@jdoss regarding problem 1: i think this is not directly related to this driver. Nomad uses, by default, the bin-pack strategy to run tasks. It will always try to fill-up...

Hi @blmhemu . The API / rootless problem is very likely a duplicate of #92. Maybe you want to try a build from main branch? Regarding the socket path: yeah,...

> One solution can be along with uid check, we should check if podman.sock exists. And if both fails, we can iterate over all /run/user//podman to find any podman.sock and...