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

Podman - Fedora doesn't use Apparmor #1783

Closed
metal3d opened this issue Aug 14, 2020 · 2 comments
Closed

Podman - Fedora doesn't use Apparmor #1783

metal3d opened this issue Aug 14, 2020 · 2 comments

Comments

@metal3d
Copy link

metal3d commented Aug 14, 2020

Hello,

Using kind 0.8.1, I want to use podman instead of Docker and Moby. When I try to create a simple cluster, it stays that I don't have apparmor on my system.

Apparmor is not usable on Fedora (we use SELinux) - is there a way to avoid "kind" to append the option for "apparmor profile" ?

$ kind create cluster
enabling experimental podman provider
Creating cluster "kind" ...
podman provider may not work properly in rootless mode
 ✓ Ensuring node image (kindest/node:v1.18.2) 🖼
 ✗ Preparing nodes 📦 
ERROR: failed to create cluster: podman run error: command "podman run --hostname kind-control-plane --name kind-control-plane --label io.x-k8s.kind.role=control-plane --privileged --security-opt seccomp=unconfined --security-opt apparmor=unconfined --tmpfs /tmp --tmpfs /run --volume /var --volume /lib/modules:/lib/modules:ro --detach --tty --label io.x-k8s.kind.cluster=kind --publish=127.0.0.1:37487:6443/TCP kindest/node@sha256:7b27a6d0f2517ff88ba444025beae41491b016bc6af573ba467b70c5e8e0d85f" failed with error: exit status 125
Command Output: Error: Apparmor profile "unconfined" specified, but Apparmor is not enabled on this system

Thanks a lot

@metal3d
Copy link
Author

metal3d commented Aug 14, 2020

OK, duplicated #1757

@metal3d metal3d closed this as completed Aug 14, 2020
@BenTheElder
Copy link
Member

indeed fedora does not, but docker gracefully handles this. podman broke this flag in 2.x

this is why we have podman specific codepaths, instead of being able to just support "docker"=>"podman"

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

No branches or pull requests

2 participants