Public bug reported:
On a fresh Ubuntu Xenial 16.04 LTS Server install, the boot stalls for
exactly 90 seconds when using a fairly complex partitioning setup. After
this, everything works as expected.
The partitioning is as follows:
/sda GPT
/sda1 ESP (/boot/efi)
/sda2 raid1 md0 ext4 (/boot)
** Description changed:
- fstrun daily cronjob output in an unprivileged LXD container:
+ fstrun weekly cronjob output in an unprivileged LXD container:
/etc/cron.weekly/fstrim:
fstrim: cannot open /dev/.lxd-mounts: Permission denied
fstrim: /dev/fuse: not a directory
fstrim: /dev/lxd:
Public bug reported:
The following simple netplan config results in a 2-minut unneccessary
delay on boot. Everything works like it should in the end. The bridge
has no interfaces due to a regression in Ubuntu migrating to netplan
(see
Workaround:
echo "Set disable_coredump false" | sudo tee -a /etc/sudo.conf
** Also affects: lxd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sudo in Ubuntu.
Container management seems to be the source of the error, sudo just
suppresses it. So a potential fix is in LXD or related packages.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sudo in Ubuntu.
This is fairly problematic when core functionality that is orchestrated
in the cloud moves from deb to snap. In our example, lxc (LXD command
line tool) was assumed to be in the path when building the
orchestration. Using the full path makes it less portable. It also makes
managing multiple
Digging even further back, it turns out that IFDOWN is in itself a
workaround for an equal issue dating back to ~2012. As such, the core of
the issue lies with how initramfs network setup overrides netplan.
Adding that package.
Given the very limited setup /etc/initramfs-tools/initramfs.conf
Public bug reported:
Since initramfs networking is rather limited, a simple flag to reset
networking afterwards (or not to generate netplan files) would be
valuable. The intended effect is to allow fully featured networking
tools to set up the network afterwards.
Use cases include the following,
It seems the workaround above does not work on Ubuntu 20.04.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1813394
Title:
DROPBEAR_IFDOWN=* takes interface down
Which version of Mint (or which upstream Ubuntu it is based on?) I
wonder if there is a way to get those rows into the configs rather than
editing packaged files?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
I can confirm the workaround by boxeus works on Ubuntu 20.04 LTS. To
improve on that, the lines can be added to the /etc/dropbear-
initramfs/config config file instead to avoid upgrade issues. It is
loaded towards the end of /usr/share/initramfs-tools/scripts/init-
bottom/dropbear anyway.
Indeed, looks like this issue is related to initramfs-tools, be that
through an incompatibility introduced in either.
I tested with the package in Debian Sid dropbear-initramfs (2024.84-1)
and got the same error. Meanwhile, on a Debian Sid install, it works.
Based on the above, I added
12 matches
Mail list logo
