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

play kube should honor container.seccomp.security.alpha.kubernetes.io #3111

Closed
AkihiroSuda opened this issue May 12, 2019 · 8 comments · Fixed by #4528
Closed

play kube should honor container.seccomp.security.alpha.kubernetes.io #3111

AkihiroSuda opened this issue May 12, 2019 · 8 comments · Fixed by #4528
Labels
do-not-close Good First Issue This issue would be a good issue for a first time contributor to undertake. kind/feature Categorizes issue or PR as related to a new feature. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. stale-issue

Comments

@AkihiroSuda
Copy link
Collaborator

Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)

Not sure /kind bug or /kind feature.
Probably /kind feature.

Description

play kube should honor container.seccomp.security.alpha.kubernetes.io
And also container.apparmor.security.beta.kubernetes.io

Steps to reproduce the issue:

Play-kube the following yaml

apiVersion: v1
kind: Pod
metadata:
  name: bk
  annotations:
    container.apparmor.security.beta.kubernetes.io/bk: unconfined
    container.seccomp.security.alpha.kubernetes.io/bk: unconfined
spec:
  containers:
  - name: bk
    image: moby/buildkit:master-rootless
    imagePullPolicy: Always
    args:
    - --oci-worker-no-process-sandbox

Describe the results you received:
Doesn't work because seccomp is not unconfined

Describe the results you expected:
seccomp should be unconfined

Additional information you deem important (e.g. issue happens only occasionally):

Output of podman version:

Version:            1.3.0-dev
RemoteAPI Version:  1
Go Version:         go1.12.2
OS/Arch:            linux/amd64

Output of podman info --debug:

debug:
  compiler: gc
  git commit: ""
  go version: go1.12.2
  podman version: 1.3.0-dev
host:
  BuildahVersion: 1.8-dev
  Conmon:
    package: podman-1.3.0-21.dev.gitb01fdcb.fc31.x86_64
    path: /usr/libexec/podman/conmon
    version: 'conmon version 1.12.0-dev, commit: 3c163e4635ea7ed15cde0814e3bbf87fb759ee25'
  Distribution:
    distribution: fedora
    version: "31"
  MemFree: 1470832640
  MemTotal: 4108623872
  OCIRuntime:
    package: runc-1.0.0-92.dev.gitc1b8c57.fc31.x86_64
    path: /usr/bin/runc
    version: |-
      runc version 1.0.0-rc7+dev
      commit: 82c0db510c11ff6ea97d86b5a4f441d8b5376a84
      spec: 1.0.1-dev
  SwapFree: 2109730816
  SwapTotal: 2147479552
  arch: amd64
  cpus: 2
  hostname: fb4099539e47
  kernel: 5.0.0-13-generic
  os: linux
  rootless: false
  uptime: 22h 37m 52.75s (Approximately 0.92 days)
insecure registries:
  registries: []
registries:
  registries:
  - docker.io
  - registry.fedoraproject.org
  - quay.io
  - registry.access.redhat.com
  - registry.centos.org
store:
  ConfigFile: /etc/containers/storage.conf
  ContainerStore:
    number: 2
  GraphDriverName: vfs
  GraphOptions:
  - overlay.mountopt=nodev
  GraphRoot: /var/lib/containers/storage
  GraphStatus: {}
  ImageStore:
    number: 2
  RunRoot: /var/run/containers/storage
  VolumePath: /var/lib/containers/storage/volumes

Additional environment details (AWS, VirtualBox, physical, etc.):

@baude baude added the kind/feature Categorizes issue or PR as related to a new feature. label May 12, 2019
@vrothberg vrothberg added the Good First Issue This issue would be a good issue for a first time contributor to undertake. label May 13, 2019
@vrothberg
Copy link
Member

Hi @AkihiroSuda, thanks for opening the issue! @baude, I also added the good first issue label. I think it's a nice task for interns.

@weirdwiz weirdwiz self-assigned this May 14, 2019
@rhatdan
Copy link
Member

rhatdan commented Jun 8, 2019

@weirdwiz Any progress on this?

@weirdwiz
Copy link
Collaborator

weirdwiz commented Jun 9, 2019

There was a failure in podman play when I started working on this, after that I couldn't get a chance to work on this. I shall look into this again.

@rhatdan
Copy link
Member

rhatdan commented Aug 5, 2019

@haircommander PTAL

@haircommander haircommander self-assigned this Aug 5, 2019
@rhatdan rhatdan assigned ashley-cui and unassigned weirdwiz Aug 10, 2019
@rhatdan
Copy link
Member

rhatdan commented Aug 10, 2019

@haircommander Any progress?

@github-actions
Copy link

github-actions bot commented Nov 4, 2019

This issue had no activity for 30 days. In the absence of activity or the "do-not-close" label, the issue will be automatically closed within 7 days.

@TomSweeneyRedHat
Copy link
Member

Just going to add a comment as this would be a nice to have.

@rhatdan
Copy link
Member

rhatdan commented Nov 4, 2019

Yes, I think I will go through some of these play kube issues and implement them.

@github-actions github-actions bot added the locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. label Sep 23, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 23, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
do-not-close Good First Issue This issue would be a good issue for a first time contributor to undertake. kind/feature Categorizes issue or PR as related to a new feature. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. stale-issue
Projects
None yet
Development

Successfully merging a pull request may close this issue.

9 participants