Skip to content

config: add CAP_SETFCAP to the default capabilities#69

Merged
rhatdan merged 1 commit into
containers:masterfrom
giuseppe:add-setfcap
Feb 20, 2020
Merged

config: add CAP_SETFCAP to the default capabilities#69
rhatdan merged 1 commit into
containers:masterfrom
giuseppe:add-setfcap

Conversation

@giuseppe

Copy link
Copy Markdown
Member

it is needed by Buildah to set file capabilities.

Signed-off-by: Giuseppe Scrivano gscrivan@redhat.com

More details here: podman-container-tools/buildah#2176

it is needed by Buildah to set file capabilities.

Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
@rhatdan

rhatdan commented Feb 20, 2020

Copy link
Copy Markdown
Member

Would it be better to add this directly to buildah rather then make podman have it by default?

@giuseppe

Copy link
Copy Markdown
Member Author

Would it be better to add this directly to buildah rather then make podman have it by default?

AFAICS, podman already has it by default:

$ podman run --rm -ti fedora getpcaps 1
Capabilities for `1': = cap_chown,cap_dac_override,cap_fowner,cap_fsetid,cap_kill,cap_setgid,cap_setuid,cap_setpcap,cap_net_bind_service,cap_net_raw,cap_sys_chroot,cap_mknod,cap_audit_write,cap_setfcap+eip

In the original issue, it was reported that the same Dockerfile works through Podman since the capability is present

@rhatdan

rhatdan commented Feb 20, 2020

Copy link
Copy Markdown
Member

Ok, maybe I removed it by accident. It should be the same as the Docker defaults.

@rhatdan rhatdan merged commit 5f0d6c3 into containers:master Feb 20, 2020
M1cha pushed a commit to M1cha/common that referenced this pull request Dec 20, 2022
…c-0.2.107

build(deps): bump libc from 0.2.106 to 0.2.107
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants