Upstream fault report:
https://github.com/containerd/containerd/issues/10542
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/2072452
Title:
AppArmor denies crun sending
unknown error after kill: runc did not terminate successfully: exit
status 1: unable to signal init: permission denied
** Also affects: runc (Ubuntu)
Importance: Undecided
Status: New
** Bug watch added: github.com/containerd/containerd/issues #10542
https://github.com/containerd/con
If the fix is not in the security pocket, how does it get sorted if the
updates pocket is turned off?
I understood *-updates are only supposed to be recommended.
As I mentioned if you build an image with a tool like 'mkosi' which utilises
debootstrap and then cleans the cache, the partial direc
Public bug reported:
Clicking 'disable' on the IPv6 tag doesn't appear to remove auto-
configured IPv6 addresses or turn off the IPv6 operations on the
specified interface.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: network-manager 1.22.8-1ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-14.
"I think you're trying to start dhclient on an interface that's already
setup."
It just triggers a lease refresh on the existing interface, which has
the same issue.
Nov 15 14:17:10 srv-ywz63 systemd-logind[981]: New session 27 of user ubuntu.
Nov 15 14:17:10 srv-ywz63 systemd[1]: Started Session
LGTM on bionic
ubuntu@srv-ywz63:~$ dpkg -l systemd | grep ii
ii systemd237-3ubuntu10.32 i386 system and service manager
ubuntu@srv-ywz63:~$ journalctl -b -u systemd-resolved | grep Started
Nov 14 17:05:43 srv-ywz63 systemd[1]: Started Network Name Resolution.
Nov 14 17:05:44 srv-y
I think just a delta change process would be fine. It's restarting when
there is no change in lease details, and just clogging up the logs.
btw I am not suggesting leaving dhclient there is a bug - hence the
title of the bug.
--
You received this bug notification because you are a member of Ubun
Public bug reported:
ping to a mapped address
ping :::216.58.213.68
sends an ICMPv6 packet out onto the Internet with the mapped address in
the destination packet and the IPv6 address as the source. Mapped
addresses shouldn't appear on the public internet according to the RFC.
I would have
Added both cloud-ini t and init-system-helpers from proposed to the
standard Xenial cloud image
(com.ubuntu.cloud:released:download/com.ubuntu.cloud:server:16.04:amd64/20160907.1/disk1.img)
on a suitably sized server.
Reset the cloud init with rm -rf /var/lib/cloud/instances/*, shutdown
the server
Have we back ported the init-system-helpers changes to Xenial?
I'm only seeing 1.29ubuntu2 this morning.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to init-system-helpers in
Ubuntu.
https://bugs.launchpad.net/bugs/1576692
10 matches
Mail list logo