[Bug 1347020] Re: systemd does not boot in a container
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 the container, do a ' ln -sf upstart /sbin/init', logout and force a lxc-stop/start of the container and do the remaining things ... -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1347020 Title: systemd does not boot in a container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1347020/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1347020] Re: systemd does not boot in a container
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 at all? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1347020 Title: systemd does not boot in a container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1347020/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1432683] Re: apt-get install lxc doesn't load required apparmor profiles
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 up, other depending services like autofs
doesn't come up either.
The problem seems to be /lib/init/apparmor-profile-load as well, which returns
with 1 and thus probably causes start always fail.
As a workaround I modified /etc/init/sssd.conf:
...
pre-start script
test -f /etc/sssd/sssd.conf || { stop; exit 0; }
/lib/init/apparmor-profile-load usr.sbin.sssd || true
end script
...
which makes it work, however, I still wonder, what apparmor-profile-load
causes to return != 0 ...
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to init-system-helpers in Ubuntu.
https://bugs.launchpad.net/bugs/1432683
Title:
apt-get install lxc doesn't load required apparmor profiles
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1432683/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1424233] Re: RFE lxc: lxc should do a better jon of housekeeping containers
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 either contains the symlinks to the real zone configs OR the real config fails itself - since they usually contain lxc.rootfs = ..., there is not really a need, to keep it in its original place. And last but not least, IMHO LXC should have an interest to make things easy to manage for the users, otherwise there is no wonder, why everyone is talking about docker but not about lxc ... -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1424233 Title: RFE lxc: lxc should do a better jon of housekeeping containers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1424233/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1424253] Re: RFE: procps tools should support lxc
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 of the box, but 'til than, it remains a distribution thing. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1424253 Title: RFE: procps tools should support lxc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1424253/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1424253] [NEW] RFE: procps tools should support lxc
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|pgrep|pkill|top} ... -z $myzone
# show zone name as well
{ps|top} -Z
** Affects: lxc (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1424253
Title:
RFE: procps tools should support lxc
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1424253/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1424233] Re: RFE lxc: lxc should do a better jon of housekeeping containers
** Package changed: upstart (Ubuntu) = lxc (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1424233 Title: RFE lxc: lxc should do a better jon of housekeeping containers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1424233/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1418279] [NEW] Automount NFSv4 doesn't work
Public bug reported:
I'm trying to use NFSv4 automount within an lxc container, however, it
doesn't work (it works for Solaris zones, so that's not an server
issue).
cd /net/pkg/TAB
/net/pkg/ not found
cat /etc/auto.master
/net-hosts
+dir:/etc/auto.master.d
+auto.master
The following log message makes me suspicious (comes 3-4 times):
[Feb 5 01:51] audit: type=1400 audit(1423099036.365:94): apparmor=DENIED
operation=mount info=failed flags match error=-13
profile=lxc-container-default name=/tmp/autoHBYlmU/ pid=27748 comm=mount
srcname=/tmp/autogYuIlN/ flags=rw, bind
But AFAICS rw,bind is allowed:
cat /etc/apparmor.d/lxc/lxc-default
profile lxc-container-default flags=(attach_disconnected,mediate_deleted) {
deny mount fstype=devpts,
mount options=(rw, rbind),
mount fstype=nfs,
mount fstype=nfs4,
mount fstype=rpc_pipefs,
mount fstype=autofs,
}
That's the profile in the global/parent zone used by all our containers. So not
sure, whether it is actually a NFSv4 or apparmor bug ...
** Affects: autofs (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to autofs in Ubuntu.
https://bugs.launchpad.net/bugs/1418279
Title:
Automount NFSv4 doesn't work
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1418279/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1394263] Re: lxc: unconditional overwrite of USE_LXC_BRIDGE
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 ... -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1394263 Title: lxc: unconditional overwrite of USE_LXC_BRIDGE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1394263/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1394249] [NEW] lxc package dependencies over-constrained
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/redundant aka non-green services like the dnsmasq stuff. ** Affects: lxc (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1394249 Title: lxc package dependencies over-constrained To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1394249/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1394263] [NEW] lxc: unconditional overwrite of USE_LXC_BRIDGE
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 Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1394263 Title: lxc: unconditional overwrite of USE_LXC_BRIDGE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1394263/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1394352] [NEW] apparmor: Multiple definitions ... bailing out
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 should put
its temp. stuff to its own private directory, if it really needs to make
a copy of whatever
E.g.: ( lxc-default == package delivered original)
ls -l /etc/apparmor.d/lxc
total 40
-rw-r--r-- 1 root root 506 Nov 19 21:34 lxc-default
-rw-r--r-- 1 root root 544 Oct 10 06:53 lxc-default-with-mounting
-rw-r--r-- 1 root root 588 Oct 10 06:53 lxc-default-with-nesting
sudo sed -e '/}/ i\\tmount options (rw, bind),' -i
/etc/apparmor.d/lxc/lxc-default
sudo apparmor_parser -r /etc/apparmor.d/lxc-containers
: AppArmor parser error for /etc/apparmor.d/lxc-containers in
/etc/apparmor.d/lxc/lxc-default at line 11: Found unexpected character: '('
ls -l /etc/apparmor.d/lxc
total 40
-rw-r--r-- 1 root root 506 Nov 19 21:35 lxc-default
-rw-r--r-- 1 root root 544 Oct 10 06:53 lxc-default-with-mounting
-rw-r--r-- 1 root root 588 Oct 10 06:53 lxc-default-with-nesting
-rw-r--r-- 1 root root 479 Nov 19 21:34 lxc-defaulte
# fix it:
sed -e '/mount options/ s,options ,options=,' -i
/etc/apparmor.d/lxc/lxc-default
sudo apparmor_parser -r /etc/apparmor.d/lxc-containers
: Multiple definitions for profile lxc-container-default exist,bailing out.
** Affects: lxc (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1394352
Title:
apparmor: Multiple definitions ... bailing out
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1394352/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1393611] Re: pax is not POSIX compliant
** Package changed: ubuntu = pax (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to pax in Ubuntu. https://bugs.launchpad.net/bugs/1393611 Title: pax is not POSIX compliant To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pax/+bug/1393611/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
