Ok, thanks for the clarification.
On Sun, Aug 6, 2023 at 10:32 PM Mantas Mikulėnas wrote:
> As far as I know, that's normal – /proc/meminfo always reflects the total
> amount of memory, regardless of cgroup limits. LXC uses lxcfs to mount a
> fake meminfo file there, nspawn doesn't have an equiv
As far as I know, that's normal – /proc/meminfo always reflects the total
amount of memory, regardless of cgroup limits. LXC uses lxcfs to mount a
fake meminfo file there, nspawn doesn't have an equivalent.
On Sun, Aug 6, 2023, 18:55 Paulo Coghi - Coghi IT
wrote:
> I used "systemctl set-property
I used "systemctl set-property systemd-nspawn@my-container-real-name.service
MemoryMax=2G", to test defining a limit on RAM usage of a nspawn container.
But after setting the limit, with the config being created at
"/etc/systemd/system.control/" correctly, when I start the container and
enter on i
On 2023-08-06 03:42, Ross Boylan wrote:
On Fri, Aug 4, 2023 at 4:32 PM Kevin P. Fleming
wrote:
On Fri, Aug 4, 2023, at 18:11, Ross Boylan wrote:
Theory: since br0 has no associated IP address when socket creation is
attempted, the socket creation fails. If so, I need to delay socket
startup
