[Bug 1419554] Re: Can't upgrade procps in LXC 1.1
Stéphane Graber
stgraber at stgraber.org
Tue Feb 10 21:26:11 UTC 2015
root at precise-procps:/root# cat /etc/sysctl.d/*.conf /etc/sysctl.conf | sysctl -e -p - || echo fail
error: "Read-only file system" setting key "kernel.printk"
net.ipv6.conf.all.use_tempaddr = 2
net.ipv6.conf.default.use_tempaddr = 2
error: "Read-only file system" setting key "kernel.kptr_restrict"
net.ipv4.conf.default.rp_filter = 1
net.ipv4.conf.all.rp_filter = 1
error: "Read-only file system" setting key "kernel.yama.ptrace_scope"
error: "Read-only file system" setting key "vm.mmap_min_addr"
fail
root at precise-procps:/root# ls
procps_3.2.8-11ubuntu6.4_amd64.deb
root at precise-procps:/root# dpkg -i procps_3.2.8-11ubuntu6.4_amd64.deb
(Reading database ... 13317 files and directories currently installed.)
Preparing to replace procps 1:3.2.8-11ubuntu6.3 (using procps_3.2.8-11ubuntu6.4_amd64.deb) ...
Unpacking replacement procps ...
Setting up procps (1:3.2.8-11ubuntu6.4) ...
procps stop/waiting
Processing triggers for ureadahead ...
Processing triggers for libc-bin ...
ldconfig deferred processing now taking place
root at precise-procps:/root# cat /etc/sysctl.d/*.conf /etc/sysctl.conf | sysctl -e -p - || echo fail
error: "Read-only file system" setting key "kernel.printk"
net.ipv6.conf.all.use_tempaddr = 2
net.ipv6.conf.default.use_tempaddr = 2
error: "Read-only file system" setting key "kernel.kptr_restrict"
net.ipv4.conf.default.rp_filter = 1
net.ipv4.conf.all.rp_filter = 1
error: "Read-only file system" setting key "kernel.yama.ptrace_scope"
error: "Read-only file system" setting key "vm.mmap_min_addr"
root at precise-procps:/root#
** Tags removed: verification-needed
** Tags added: verification-done-precise
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to procps in Ubuntu.
https://bugs.launchpad.net/bugs/1419554
Title:
Can't upgrade procps in LXC 1.1
Status in procps package in Ubuntu:
Fix Committed
Status in procps source package in Precise:
Fix Committed
Status in procps source package in Trusty:
Fix Committed
Status in procps source package in Utopic:
Fix Committed
Status in procps source package in Vivid:
Fix Committed
Bug description:
== SRU ==
Rationale:
sysctl now fails with current LXC as files which shouldn't be written to in containers are read-only. A previous fix applied to the EACCESS case as returned by apparmor.
Text case:
start procps
Regression potential:
All EROFS write failures will now be ignored (an error is still logged) but I can't think of a case where that'd be a bad thing.
Original bug report:
LXC 1.1 on vivid has started giving privileged containers a read-only
/sys, which prevents Ubuntu's procps Upstart job from starting. This
isn't normally too problematic, except that the weekend's procps SRU's
postinst tries to start the job and causes the upgrade to fail.
Disabling the procps postinst makes apt usable again.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1419554/+subscriptions
More information about the foundations-bugs
mailing list