-
Notifications
You must be signed in to change notification settings - Fork 18.9k
Closed
Labels
area/security/apparmorkind/bugBugs are bugs. The cause may or may not be known at triage time so debugging may be needed.Bugs are bugs. The cause may or may not be known at triage time so debugging may be needed.version/1.11
Milestone
Description
Output of docker version:
Client:
Version: 1.11.2
API version: 1.23
Go version: go1.6.2
Git commit: 9e83765
Built:
OS/Arch: linux/amd64
Server:
Version: 1.11.2
API version: 1.23
Go version: go1.6.2
Git commit: 9e83765
Built:
OS/Arch: linux/amd64
Output of docker info:
Containers: 0
Running: 0
Paused: 0
Stopped: 0
Images: 6
Server Version: 1.11.2
Storage Driver: btrfs
Build Version: Btrfs v4.5.3+20160516
Library Version: 101
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
Volume: local
Network: bridge null host
Kernel Version: 4.4.3-0.gedb49cc-default
Operating System: openSUSE Tumbleweed (20160709) (x86_64)
OSType: linux
Architecture: x86_64
CPUs: 8
Total Memory: 15.58 GiB
Name: f22
ID: 7CRD:N73Y:7HWT:3SJG:UT5P:346M:6KYO:KAJK:TYBJ:NQXT:DZB4:7AH5
Docker Root Dir: /var/lib/docker
Debug mode (client): false
Debug mode (server): false
Registry: https://index.docker.io/v1/
WARNING: No swap limit support
WARNING: No kernel memory limit support
Additional environment details (AWS, VirtualBox, physical, etc.):
physical
Steps to reproduce the issue:
- Disable AppArmor service.
- Place
/etc/apparmor.d/on read-only partition. - Try to start Docker daemon.
Describe the results you received.
level=fatal msg="Error starting daemon: AppArmor enabled on system but the docker-default profile could not be loaded.
Describe the results you expected:
Docker daemon starts successfully.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
area/security/apparmorkind/bugBugs are bugs. The cause may or may not be known at triage time so debugging may be needed.Bugs are bugs. The cause may or may not be known at triage time so debugging may be needed.version/1.11