From: William Hubbs <williamh@gentoo.org>
To: gentoo development <gentoo-dev@lists.gentoo.org>
Subject: [gentoo-dev] should /etc/init.d/sysctl be run in lxc guests?
Date: Thu, 3 Jul 2014 11:02:29 -0500 [thread overview]
Message-ID: <20140703160229.GA4189@linux1> (raw)
[-- Attachment #1: Type: text/plain, Size: 652 bytes --]
This is a question to lxc users, since I don't run it.
I have a bug against OpenRC in which the user is saying that I should
allow /etc/init.d/sysctl to run inside an lxc container [1].
My understanding is that this is not a good idea since an lxc container
actually changes settings in the host's kernel.
The user's position seems to be that it should be up to the lxc
template or the sys admin to make sure they configure things correctly.
Does anyone have any thoughts? Is this something I should allow people
to shoot themselves in the foot with if they do something wrong?
Thanks,
William
[1] https://bugs.gentoo.org/show_bug.cgi?id=516050
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next reply other threads:[~2014-07-03 16:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-03 16:02 William Hubbs [this message]
2014-07-03 20:12 ` [gentoo-dev] should /etc/init.d/sysctl be run in lxc guests? Sergey Popov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140703160229.GA4189@linux1 \
--to=williamh@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox