Hi folks,
I'm trying to run the avahi daemon in my containers, but I'm running
into this error:
fork() failed: Resource temporarily unavailable
Avahi starts fine in the first container, but starting it in any
subsequent starting attempts result in the above error.
This issue was raised befo
User namespaces in recent kernels will probably not be usable for
containers. Eric is heavily developing them right now, and hopefully
in the next 6-12 months they'll be fully supported.
So if you can't run an older kernel, I guess I'd recommend running a
custom avahi package without the 3-task l
Hi Serge,
> User namespaces in recent kernels will probably not be usable for
> containers. Eric is heavily developing them right now, and hopefully
> in the next 6-12 months they'll be fully supported.
Right, so I guess enabling them by default isn't a good idea right now
:-)
> So if you can't
Hi folks,
while writing scripts, I occasionally miss an lxc-config command, that
can parse (and possibly also write) the lxc config files for me in a
robust way. Sure, it's an easy format to just grep and sed over (or at
least it looks like that at first glance), but that's not very
future-proof o
