Here is an interesting discussion in cilium thread
https://issueexplorer.com/issue/cilium/cilium/17647
Package: src:linux
Version: 4.19.208-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
* What led up to the situation?
Regular "apt upgrade" made kubernetes cluster driven by cilium unusable
* What exactly did you do (or not do) that was effective (or ineffective)?
Package: cloud-init
Version: 20.2-2~deb10u2
Severity: important
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
I use "ca-certs" to supply additional certificates. With just one certiticate
everything
works as expected, however when provided more
Hi
I believe it can be found here https://github.com/systemd/systemd/pull/5499
On Sat, 22 Dec 2018 at 23:47, Michael Biebl wrote:
> Control: tags -1 + moreinfo
>
> Am 23.12.18 um 00:29 schrieb Vladimir Tiukhtin:
> > Docker limits this system call be default. However RedHat image
Package: systemd
Version: 232-25+deb9u6
Running Debian Stretch in docker container results in
Failed to determine whether /sys is a mount point: Operation not permitted
Failed to determine whether /proc is a mount point: Operation not permitted
Failed to determine whether /dev is a mount point:
Apr 2017, Vladimir Tiukhtin wrote:
>
>> Package: keepalived
>> Version: 1:1.3.2-1
>> Severity: normal
>>
>> Dear Maintainer,
>>
>>* What led up to the situation?
>> Using systemd-networkd with keepalived
> I don't think we (Debian) already sup
Package: keepalived
Version: 1:1.3.2-1
Severity: normal
Dear Maintainer,
* What led up to the situation?
Using systemd-networkd with keepalived
* What exactly did you do (or not do) that was effective (or ineffective)?
Start systemd-networkd. Start keepalived. Check VIP is applyed.
7 matches
Mail list logo
