hi Michael,
I currently can't test that. Given that bullseye isn't released yet, I
don't have a test environment here.
When bullseye is released I will try to test it again, for time being I
have moved all libvirt-lxc container to use lxc.
Regards,
Maximilian Philipps
PM, Adam D. Barratt wrote:
> On 2020-03-02 14:53, Maximilian Philipps wrote:
>> When calling debuild with the -e parameter the arguments gets
>> interpolated into the Changed-By field of the .changes file.
>>
>> From our build job:
>>
>> debuild -b -us -uc -e
Package: devscripts
Version: 2.19.5+deb10u1
hi.
When calling debuild with the -e parameter the arguments gets
interpolated into the Changed-By field of the .changes file.
>From our build job:
debuild -b -us -uc -eDEB_BUILD_OPTIONS=parallel=2 -ai386
grep 'Changed-By:' *.changes
Changed-By: D
hi
I can now reliably trigger the 8 exabyte issue. When I start a
libvirt-lxc container, libvirts sets the memory limit.
This can be seen with:
cat
/sys/fs/cgroup/memory/machine.slice/machine-lxc\x2d27166\x2dhost.domain.tld.scope/memory.limit_in_bytes
2147483648
If I now call systemctl daemon-
hi,
After digging a bit more, it appears that after the update from stretch
to buster we are using some mix cgroupv1 and cgroupv2.
/sys/fs/cgroup/ is still a tmpfs and /sys/fs/cgroup/unified/ exits, but
hast no controllers. So apparently systemd should still use the
controllers from v1 with the h
Recently updated one of the hosts and the containers running on it from
stretch to buster.
With buster's 241-7~deb10u1 the issue still exists. I have tried working
around this issue by setting a memory limit on the -.slice from within
the container, but this is fairly unreliable.
On 02/19/2018 02:07 PM, Maximilian Philipps wrote:
On 02/19/2018 01:50 PM, Michael Biebl wrote:
Am 19.02.2018 um 13:09 schrieb Maximilian Philipps:
Package: systemd
Version: 232-25+deb9u1
Severity: important
Hi
I have an issue with Systemd unsetting the memory limit for my
container
On 02/19/2018 01:50 PM, Michael Biebl wrote:
Am 19.02.2018 um 13:09 schrieb Maximilian Philipps:
Package: systemd
Version: 232-25+deb9u1
Severity: important
Hi
I have an issue with Systemd unsetting the memory limit for my container,
whereupon programs like free and htop report having
Package: systemd
Version: 232-25+deb9u1
Severity: important
Hi
I have an issue with Systemd unsetting the memory limit for my container,
whereupon programs like free and htop report having access to 8 exabyte
of memory.
The setup is the following:
Host:
Release: Debian jessie
Kernel: 4.9.65-3+
9 matches
Mail list logo
