Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

containers.conf: add privileged field to containers table #1683

Merged
merged 1 commit into from
Oct 5, 2023

Conversation

vrothberg
Copy link
Member

As requested in containers/podman/issues/20000, add a privileged field to the containers table in containers.conf. I was hesitant to add such a field at first (for security reasons) but I understand that such a field can come in handy when using modules - certain workloads require a privileged container.

@flouthoc @giuseppe @rhatdan PTAL

@Luap99
Copy link
Member

Luap99 commented Oct 4, 2023

Dup of #1678?! And the same question, is it really to much work to set the proper security options one by one instead of using the big hammer?

@vrothberg
Copy link
Member Author

Oh boy, I didn't see the other PR at all.

is it really to much work to set the proper security options one by one instead of using the big hammer?

As mentioned in the commit message, I am not a huge fan either. But in some cases it probably is too much work or too complex. In many cases the users are not developers/SWEs. I prefer to have some "modules" using privileged than users developing the habit to always use the --privileged flag.

@rhatdan, I don't mind using your PR or this one. I plumbed this one here into Podman in containers/podman#20252.

@rhatdan
Copy link
Member

rhatdan commented Oct 4, 2023

LGTM
But I would suggest a little stronger language in the man page.

I had

Run all containers in privileged mode. The privileged field should almost
never be set, containers running in privileged mode have no separation from
the host other then namespaces. This means they can easily break out of
confinement.

pkg/config/containers.conf Outdated Show resolved Hide resolved
As requested in containers/podman/issues/20000, add a `privileged` field
to the containers table in containers.conf.  I was hesitant to add such
a field at first (for security reasons) but I understand that such a
field can come in handy when using modules - certain workloads require a
privileged container.

Signed-off-by: Valentin Rothberg <vrothberg@redhat.com>
@vrothberg
Copy link
Member Author

Updated. Tried integrating @rhatdan's text with the other one (that I took from Podman's man page). Will update Podman's man page as well when doing the final vendor.

Copy link
Member

@Luap99 Luap99 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 5, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Luap99, vrothberg

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@rhatdan
Copy link
Member

rhatdan commented Oct 5, 2023

/lgtm

@openshift-ci openshift-ci bot added the lgtm label Oct 5, 2023
@openshift-ci openshift-ci bot merged commit b4ef9cd into containers:main Oct 5, 2023
7 checks passed
@vrothberg vrothberg deleted the privileged branch October 5, 2023 12:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants