You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I tried to start AppArmor in a container and configured "apparmorProfile": "usr.bin.tcpdump" in config.cfg, using /usr/bin/tcpdump as an example. When runc started the container, the following error occurred:
run commond is :
runc --debug create test
Error log:
DEBU[0000] nsexec[58596]: => nsexec container setup
DEBU[0000] nsexec-0[58596]: ~> nsexec stage-0
DEBU[0000] nsexec-0[58596]: spawn stage-1
DEBU[0000] nsexec-0[58596]: -> stage-1 synchronisation loop
DEBU[0000] nsexec-1[58600]: ~> nsexec stage-1
DEBU[0000] nsexec-1[58600]: unshare remaining namespaces (except cgroupns)
DEBU[0000] nsexec-1[58600]: spawn stage-2
DEBU[0000] nsexec-1[58600]: request stage-0 to forward stage-2 pid (58601)
DEBU[0000] nsexec-0[58596]: stage-1 requested pid to be forwarded
DEBU[0000] nsexec-0[58596]: forward stage-1 (58600) and stage-2 (58601) pids to runc
DEBU[0000] nsexec-1[58600]: signal completion to stage-0
DEBU[0000] nsexec-2[1]: ~> nsexec stage-2
DEBU[0000] nsexec-1[58600]: <~ nsexec stage-1
DEBU[0000] nsexec-0[58596]: stage-1 complete
DEBU[0000] nsexec-0[58596]: <- stage-1 synchronisation loop
DEBU[0000] nsexec-0[58596]: -> stage-2 synchronisation loop
DEBU[0000] nsexec-0[58596]: signalling stage-2 to run
DEBU[0000] nsexec-2[1]: unshare cgroup namespace
DEBU[0000] nsexec-2[1]: signal completion to stage-0
DEBU[0000] nsexec-2[1]: <= nsexec container setup
DEBU[0000] nsexec-2[1]: booting up go runtime ...
DEBU[0000] nsexec-0[58596]: stage-2 complete
DEBU[0000] nsexec-0[58596]: <- stage-2 synchronisation loop
DEBU[0000] nsexec-0[58596]: <~ nsexec stage-0
DEBU[0000] child process in init()
ERRO[0000]utils.go:62 main.fatalWithCode() runc create failed: unable to start container process: error during container init: unable to apply apparmor profile: apparmor failed to apply profile: write /proc/self/attr/apparmor/exec: no such file or directory
I have already tried other solutions, but none of them worked. The AppArmor mechanism has been enabled on my system.
The config.cfg is below:
Description
When I tried to start AppArmor in a container and configured "apparmorProfile": "usr.bin.tcpdump" in config.cfg, using /usr/bin/tcpdump as an example. When runc started the container, the following error occurred:
run commond is :
Error log:
I have already tried other solutions, but none of them worked. The AppArmor mechanism has been enabled on my system.
The config.cfg is below:
the dmeg log:
I am not familiar with the AppArmor mechanism. If there is an issue with the AppArmor configuration, please point it out.
thanks
Steps to reproduce the issue
Describe the results you received and expected
What version of runc are you using?
runc version 1.1.0+dev
commit: v1.1.0-491-gd8a3daac
spec: 1.1.0-rc.1
go: go1.19.5
libseccomp: 2.5.3
Host OS information
PRETTY_NAME="Ubuntu 22.04.1 LTS"
NAME="Ubuntu"
VERSION_ID="22.04"
VERSION="22.04.1 LTS (Jammy Jellyfish)"
VERSION_CODENAME=jammy
ID=ubuntu
ID_LIKE=debian
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
UBUNTU_CODENAME=jammy
Host kernel information
Linux adlab-fuzz 5.19.0-38-generic #39~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Mar 17 21:16:15 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
The text was updated successfully, but these errors were encountered: