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

cgroup.event_control: operation not supported #45013

Open
rgomezceis opened this issue Feb 16, 2023 · 1 comment
Open

cgroup.event_control: operation not supported #45013

rgomezceis opened this issue Feb 16, 2023 · 1 comment
Labels
kind/bug Bugs are bugs. The cause may or may not be known at triage time so debugging may be needed. status/0-triage version/23.0

Comments

@rgomezceis
Copy link

Description

When deploying a container I have this error:

level=error msg="add cg to OOM monitor" error="write /sys/fs/cgroup/memory/docker/85658e63e3ce613704e58cdc71d9dc8ff571d980e062937fbb47d0105561e841/cgroup.event_control: operation not supported"

time="2023-02-16T12:09:32.696019615+01:00" level=info msg="loading plugin \"io.containerd.event.v1.publisher\"..." runtime=io.containerd.runc.v2 type=io.containerd.event.v1
time="2023-02-16T12:09:32.696225191+01:00" level=info msg="loading plugin \"io.containerd.internal.v1.shutdown\"..." runtime=io.containerd.runc.v2 type=io.containerd.internal.v1
time="2023-02-16T12:09:32.696560298+01:00" level=info msg="loading plugin \"io.containerd.ttrpc.v1.task\"..." runtime=io.containerd.runc.v2 type=io.containerd.ttrpc.v1
time="2023-02-16T12:09:32.697990085+01:00" level=info msg="starting signal loop" namespace=moby path=/run/docker/containerd/daemon/io.containerd.runtime.v2.task/moby/85658e63e3ce613704e58cdc71d9dc8ff571d980e062937fbb47d0105561e841 pid=14731 runtime=io.containerd.runc.v2
time="2023-02-16T12:09:34.012697746+01:00" level=error msg="add cg to OOM monitor" error="write /sys/fs/cgroup/memory/docker/85658e63e3ce613704e58cdc71d9dc8ff571d980e062937fbb47d0105561e841/cgroup.event_control: operation not supported"
INFO[2023-02-16T12:09:34.079059445+01:00] ignoring event                                container=85658e63e3ce613704e58cdc71d9dc8ff571d980e062937fbb47d0105561e841 module=libcontainerd namespace=moby topic=/tasks/delete type="*events.TaskDelete"
INFO[2023-02-16T12:09:34.080524569+01:00] shim disconnected                             id=85658e63e3ce613704e58cdc71d9dc8ff571d980e062937fbb47d0105561e841
WARN[2023-02-16T12:09:34.081323647+01:00] cleaning up after shim disconnected           id=85658e63e3ce613704e58cdc71d9dc8ff571d980e062937fbb47d0105561e841 namespace=moby
INFO[2023-02-16T12:09:34.081542468+01:00] cleaning up dead shim
WARN[2023-02-16T12:09:34.098014852+01:00] cleanup warnings time="2023-02-16T12:09:34+01:00" level=info msg="starting signal loop" namespace=moby pid=15111 runtime=io.containerd.runc.v2

Reproduce

docker run --rm hello-world

Expected behavior

No response

docker version

Client:
 Version:           23.0.1
 API version:       1.42
 Go version:        go1.19.5
 Git commit:        a5ee5b1
 Built:             Thu Feb  9 19:45:43 2023
 OS/Arch:           linux/amd64
 Context:           default

Server: Docker Engine - Community
 Engine:
  Version:          23.0.1
  API version:      1.42 (minimum version 1.12)
  Go version:       go1.19.5
  Git commit:       bc3805a
  Built:            Thu Feb  9 19:48:50 2023
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          v1.6.16
  GitCommit:        31aa4358a36870b21a992d3ad2bef29e1d693bec
 runc:
  Version:          1.1.4
  GitCommit:        v1.1.4-0-g5fd4c4d
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

docker info

Client:
 Context:    default
 Debug Mode: false
 Plugins:
  compose: Docker Compose (Docker Inc.)
    Version:  v2.16.0
    Path:     /usr/local/lib/docker/cli-plugins/docker-compose

Server:
 Containers: 0
  Running: 0
  Paused: 0
  Stopped: 0
 Images: 3
 Server Version: 23.0.1
 Storage Driver: overlay2
  Backing Filesystem: extfs
  Supports d_type: true
  Using metacopy: false
  Native Overlay Diff: true
  userxattr: false
 Logging Driver: json-file
 Cgroup Driver: cgroupfs
 Cgroup Version: 1
 Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
 Swarm: inactive
 Runtimes: io.containerd.runc.v2 runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: 31aa4358a36870b21a992d3ad2bef29e1d693bec
 runc version: v1.1.4-0-g5fd4c4d
 init version: de40ad0
 Security Options:
  seccomp
   Profile: builtin
 Kernel Version: 5.15.92-rt57-g414876561405-dirty
 Operating System: NI Linux Real-Time 9.2 (hardknott)
 OSType: linux
 Architecture: x86_64
 CPUs: 2
 Total Memory: 1.771GiB
 Name: NI-cRIO-9045-01F88633
 ID: 00a34127-331f-46f8-89aa-b6ecd8bb2ec1
 Docker Root Dir: /var/lib/docker
 Debug Mode: false
 Registry: https://index.docker.io/v1/
 Experimental: false
 Insecure Registries:
  127.0.0.0/8
 Live Restore Enabled: false
 Product License: Community Engine

Additional Info

No response

@rgomezceis rgomezceis added kind/bug Bugs are bugs. The cause may or may not be known at triage time so debugging may be needed. status/0-triage labels Feb 16, 2023
@thaJeztah
Copy link
Member

thaJeztah commented Feb 16, 2023

Looks like the error log itself comes from containerd; https://github.com/containerd/containerd/blob/v1.6.16/runtime/v2/runc/task/service.go#L168-L191

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Bugs are bugs. The cause may or may not be known at triage time so debugging may be needed. status/0-triage version/23.0
Projects
None yet
Development

No branches or pull requests

3 participants