Public bug reported:
If one starts dhcrelay with explicitly specifying the interfaces to
listen,it silently ignores these options and still listens on all
interfaces. This is neither what the man page says (it says, only if no
interface is given, it listen on all interfaces), nor what is needed. I
Hmmm, that's an old one. IIRC the real root cause was, that some files
possibly included via /usr/share/lxc/config/ubuntu.common.conf still
used lxc.cgroup.devices.* instead of lxc.cgroup2.devices.* (the machine
was upgraded from bionic to focal).
--
You received this bug notification because you
Public bug reported:
Distributor ID: Ubuntu
Description:Ubuntu 20.04.2 LTS
Release:20.04
Codename: focal
If one sets in /etc/default/grub (as e.g. desired by facebook oomd):
GRUB_CMDLINE_LINUX="systemd.unified_cgroup_hierarchy=1 swapaccount=1 ..."
lxc is not able to start any c
Public bug reported:
Distributor ID: Ubuntu
Description:Ubuntu 20.04.2 LTS
Release:20.04
Codename: focal
lxc-stop -r -n $zone
Stops the container, but does not reboot it anymore, as in bionic.
** Affects: lxc (Ubuntu)
Importance: Undecided
Status: New
--
You re
Public bug reported:
> + do-release-upgrade
Checking for a new Ubuntu release
Get:1 Upgrade tool signature [819 B]
Get:2 Upgrade tool [1,263 kB]
Fetched 1,264 kB in 0s (0 B/s)
Public bug reported:
# apt install lxc-templates
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
busybox-static cloud-image-utils debootstrap dirmngr distro-info genisoimage
gnupg gnupg-l10n gn
Public bug reported:
In bionic openssh client/server ships without blowfish-cbc, arcfour,
arcfour128, arcfour256 and cast128-cbc. Unfortunately they are required
for backward compatibility, especially for embedded devices, which do
not support other ciphers (e.g. Rittal Liquid Cooling Package for
No, this is not an option. Also note, that this breaks a lot of
workflows without reason, because Ubuntu ssh client simply stops
working with a message like "~/.ssh/config line 3: Bad SSH2 cipher spec
'...'": it simply does not know such ciphers (does not ignore them). So
especially in environment
I'm running utopic with latest updates. Any container, which has systemd
running simply hangs, when /sbin/init gets started (no matter, whether
config has 'lxc.kmsg = 0' or not). Tried it previously with a trusty and
today with a vivid container. So wondering, whether there is a bugfix
available a
It appears, that something is still broken. Because systemd doesn't
work, I installed upstart + upstart-sysv (and uninstalled systemd-
sysv), but unfortunately sssd doesn't come up (has exactly the same
config, as in other < 14.10 zones, where it works as expected). And
because sssd doesn't come u
Public bug reported:
"/bin/mount -t zfs -o defaults,atime,dev,exec,rw,suid,nomand,zfsutil
rpool/zones/bla /zones/bla"
fails, if env var POSIXLY_CORRECT is set, because it calls
"/sbin/mount.zfs rpool/zones/bla /zones/bla -o rw,zfsutil", which is obviously
a bug. Options should always come first
mount from util-linux 2.27.1 (libmount 2.27.0: selinux, assert, debug)
Description:Ubuntu 16.04.2 LTS
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1692109
Title:
AFAICS the problem is libmount/src/context_mount.c:exec_helper() which
is uses operands in a wrong/not posixly incorrect way. See also
http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap12.html
--
You received this bug notification because you are a member of Ubuntu
Touch seeded pack
Public bug reported:
When running 'apt-get update' (e.g. on a container install post-install
script), apt-get return with exit code 0, even so it wasn't able to
"update" properly. E.g.:
+ apt-get update
Err:1 http://de.archive.ubuntu.com/ubuntu xenial InRelease
Temporary failure resolving 'de.a
Hmmm, IMHO 'Err:' and 'W: Failed to fetch' indicate, that it was not
able to update properly and thus the result of the operation is
unreliable. So its like "your connection is secured, but may be not". I
guess most people wouldn't do any financial transaction when reading
this ... ;-)
--
You rec
The bug/subject here is, that apt-get doesn't return a proper exit code,
not, what else one could use to workaround the bug.
Saying, that update from one of all (i.e. 1+) sites is sufficient is
like going to fly with a jet, where one of two engines is already broken
before it starts. Making this d
Actually this is the problem: Users think, their system is up-to-date,
but it is not for sure because a site failed to respond. Therefore only
if _all_ sites answered the request properly, apt-get should return 0.
If not, it should return a specified return code, which lets the callee
know, that th
Public bug reported:
Since on common platforms ureadahead solves nothing but causes a huge
amount of garbage/totally useless error messages, which makes it really
hard to extract the important messages from e.g. journalctl output, it
should be removed from ubuntu-minimal. If there are people, who
Ćukasz Zemczak, yes, upgraded a machine from bionic to focal - same
problem. However, the patch looks not optimal but sufficient.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bu
Public bug reported:
If one creates e.g. /etc/systemd/network.cu and /etc/systemd/network.fc
and symlinks /etc/systemd/network to one of them, network setup will
fail on reboot, because /usr/share/initramfs-tools/hooks/udev does a
very poor job: it simply checks for a directory instead of the lin
Public bug reported:
Right now lxc does a pretty poor job wrt. managing containers, i.e. one
needs to know, where containers have been installed to be able to
access/use/manage them (option -P dir) unless they've been installed in
the default location. Even if one knows the install path, it is sti
** Package changed: upstart (Ubuntu) => lxc (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1424233
Title:
RFE lxc: lxc should do a better jon of housekeeping containe
Public bug reported:
Container management/monitoring is currently a pain, because procps do
not support container, i.e. there is no way to tell the tools to
"filter" the output wrt. a certain zone or to add a column, which shows
the zone name a process belongs to.
E.g. for what is needed:
{ps|pgr
Public bug reported:
'pgrep upstart-udev-bridge' should definitely spit out a pid, but it
doesn't. When one uses the option -f than it actually prints the PID of
the upstart-udev-bridge process. However using -f is a bad workaround,
because than (at least wrt. the man page) the arguments and opera
Please read carefully! This bug is not about upstart-udev-bridge or any
other service but about PGREP . 'pgrep upstart-udev-bridge' is just an
example, which should work on any Ubuntu, i.e. to reproduce the problem!
--
You received this bug notification because you are a member of Ubuntu
Touch se
Actually that's not the same at all, because $cgroup != $lxc_name . Your
workaround is absolutely user UNfriendly, i.e. still hard to read and
for casual users inconvinient, because one needs supply all that many
format options ...
Anyway, I agree, that these utils should support such things out o
Yepp, and that's IMHO a design flaw. E.g. if one wants to distribute the
load on iots storage, it might make sense, to distribute the zones of
several storage devices, e.g. zone1 on JBOD1, zone2 on JBOD2, etc
As said, the only thing, which lxc nees to track is a single "config
directory" which
Probably because this piece of junk (upstart) just silently discards any
*.conf file with errors/unknown directives in it instead of
reporting/logging the problem.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart in Ubu
Public bug reported:
Ubuntu documentation states, that changing /etc/gai.conf is the way to
be able to prefer IPv4 over IPv6.
So from the original gai.conf we removed the comment in front of the precedence
statements AND set the value for :::0:0/96 to 60.
Unfortunately this does not seem to
Public bug reported:
When a users having tcsh as its [login] shell presses tab key
(autocompletion), tcsh coredumps immediately, always:
admin.python ~ > gdb tcsh
GNU gdb (Ubuntu 7.11.90.20160906-0ubuntu1) 7.11.90.20160906-git
...
(gdb) run
Starting program: /local/home/admin/tcsh
admin.python ~
Today I upgraded our last utopic containers (~10) to vivid using do-
release-upgrade: Everywhere the same: after reboot systemd is the only
thing which is running in the container, but nothing else happens. It
doesn't start anything! So the only way to get the stuff fixed is to
manually attach to t
Public bug reported:
Obviously lxc does NOT depend on dnsmasq-base and thus this dependency
should be lowered to "optional" or "recommended".
Today entities using containers already have proper DNS as well as DHCP
servers and thus do not need at all another point of failure/possible
weak software
Public bug reported:
Defining USE_LXC_BRIDGE and than overwriting it unconditionally in the
source /etc/default/lxc-net doesn't make sense/is confusing.
** Affects: lxc (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubu
Public bug reported:
When one creates a incorrect profile, apparmor_parser seems to leave an
artifact of the "problem" file in the same directory, which in turn
leads to another error, when the file gets fixed. Not sure, how appamor
stuff works, but this is simply an unacceptable behavior! It shou
Well, it is strange: If there is such a setting in /etc/default/lxc, one
usually assumes, that this is the master of the disaster and gets
"propagated" downwards, but obviously it is not ... And thus I wonder,
which files in the lxc forest need to be checked as well to avoid
further surprises ...
35 matches
Mail list logo