From: Sergey Popov <pinkbyte@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] should /etc/init.d/sysctl be run in lxc guests?
Date: Fri, 04 Jul 2014 00:12:53 +0400 [thread overview]
Message-ID: <53B5B945.4060000@gentoo.org> (raw)
In-Reply-To: <20140703160229.GA4189@linux1>
[-- Attachment #1: Type: text/plain, Size: 1244 bytes --]
03.07.2014 20:02, William Hubbs пишет:
> 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
>
Comment #3 in bug mostly right. By dropping CAP_SYS_ADMIN you can
prevent of changing most of the global sysctl settings. Other settings
still can be changed by root inside the container, but these settings
are separate and unique to each container(like ip_forward and all the
network stuff that sits in network namespace).
--
Best regards, Sergey Popov
Gentoo developer
Gentoo Desktop-effects project lead
Gentoo Qt project lead
Gentoo Proxy maintainers project lead
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 555 bytes --]
prev parent reply other threads:[~2014-07-03 20:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-03 16:02 [gentoo-dev] should /etc/init.d/sysctl be run in lxc guests? William Hubbs
2014-07-03 20:12 ` Sergey Popov [this message]
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=53B5B945.4060000@gentoo.org \
--to=pinkbyte@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