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

Container Restarted: Docker shim disconnected #47757

Open
ishankgoel opened this issue Apr 25, 2024 · 1 comment
Open

Container Restarted: Docker shim disconnected #47757

ishankgoel opened this issue Apr 25, 2024 · 1 comment
Labels
area/runtime 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/25.0

Comments

@ishankgoel
Copy link

Description

Issue description:
Container stopped logging for sometime & restarted automatically.
Found this in docker logs:

messages-2024-04-02-1712016061.gz:7612:2024-04-01T00:32:23.142118+00:00 onxl9979 dockerd[56029]: time="2024-04-01T00:32:23.141970662Z" level=info msg="shim disconnected" id=15beb68826895f5ab6922c6dceac8a486883366a9ff4ebff0ae9f8da6ca968ef
messages-2024-04-02-1712016061.gz:7613:2024-04-01T00:32:23.142118+00:00 onxl9979 dockerd[56029]: time="2024-04-01T00:32:23.142102041Z" level=warning msg="cleaning up after shim disconnected" id=15beb68826895f5ab6922c6dceac8a486883366a9ff4ebff0ae9f8da6ca968ef namespace=moby
messages-2024-04-02-1712016061.gz:7614:2024-04-01T00:32:23.142714+00:00 onxl9979 dockerd[56029]: time="2024-04-01T00:32:23.142128982Z" level=info msg="cleaning up dead shim"

Docker version:

docker -v
Docker version 25.0.2, build 29cf629

Reproduce

Occurs randomly.
Cannot reproduce manually

Expected behavior

No response

docker version

Client: Docker Engine - Community
 Version:           25.0.2
 API version:       1.44
 Go version:        go1.21.6
 Git commit:        29cf629
 Built:             Thu Feb  1 00:24:06 2024
 OS/Arch:           linux/amd64
 Context:           default

Server: Docker Engine - Community
 Engine:
  Version:          25.0.2
  API version:      1.44 (minimum version 1.24)
  Go version:       go1.21.6
  Git commit:       fce6e0c
  Built:            Thu Feb  1 00:23:02 2024
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.6.28
  GitCommit:        ae07eda36dd25f8a1b98dfbf587313b99c0190bb
 runc:
  Version:          1.1.12
  GitCommit:        v1.1.12-0-g51d5e94
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

docker info

Client: Docker Engine - Community
 Version:    25.0.2
 Context:    default
 Debug Mode: false
 Plugins:
  buildx: Docker Buildx (Docker Inc.)
    Version:  v0.12.1
    Path:     /usr/libexec/docker/cli-plugins/docker-buildx
  compose: Docker Compose (Docker Inc.)
    Version:  v2.24.5
    Path:     /usr/libexec/docker/cli-plugins/docker-compose

Server:
 Containers: 78
  Running: 78
  Paused: 0
  Stopped: 0
 Images: 163
 Server Version: 25.0.2
 Storage Driver: overlay2
  Backing Filesystem: extfs
  Supports d_type: true
  Using metacopy: false
  Native Overlay Diff: false
  userxattr: false
 Logging Driver: json-file
 Cgroup Driver: systemd
 Cgroup Version: 2
 Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local splunk syslog
 Swarm: inactive
 Runtimes: docker-runc io.containerd.runc.v2 runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: ae07eda36dd25f8a1b98dfbf587313b99c0190bb
 runc version: v1.1.12-0-g51d5e94
 init version: de40ad0
 Security Options:
  seccomp
   Profile: builtin
  cgroupns
 Kernel Version: 5.15.0-101.103.2.1.el8uek.x86_64
 Operating System: Oracle Linux Server 8.8
 OSType: linux
 Architecture: x86_64
 CPUs: 48
 Total Memory: 125.2GiB
 Name: onxl7856.ott.ciena.com
 ID: b3175aa0-8a74-4998-879d-3874980777eb
 Docker Root Dir: /opt/ciena/data/docker
 Debug Mode: false
 Labels:
  host_id=4
 Experimental: false
 Insecure Registries:
  127.0.0.0/8
 Live Restore Enabled: false

Additional Info

No response

@ishankgoel ishankgoel 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 Apr 25, 2024
@cpuguy83
Copy link
Member

cpuguy83 commented May 4, 2024

There is not really a thriving to go on here.
Can you describe the problem more completely?
What is your container config? Do you know why your container exited?

Those log messages are not really abnormal.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/runtime 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/25.0
Projects
None yet
Development

No branches or pull requests

3 participants