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

Docker container exited with System error: stat /system.slice/docker.service: no such file or directory. #21444

Closed
sybrandy opened this issue Mar 23, 2016 · 3 comments

Comments

@sybrandy
Copy link

Hello,

I got the following output from a docker container that was running in Mesos via Marathon (please forgive the typos as I'm manually copying from one terminal to another :( ):

Code: System error

Message: state /system.slice/docker.service: no such file or directory

Frames:

---
0: setupRootfs
Package github.com/opencontainers/runc/libcontainer
File: rootfs_linux.go@40

---
1: Init
Package: github.com/opencontainers/runc/libcontainer.(*libStandardInit)
File: standard_init_linux.go@57

---
2: StartInitialization
Package: github.com/opencontainers/runc/libcontainer.(*LinuxFactory)
File: factory_linux.go@242

---
3: initializer
Package: github.com/docker/docker/daemon/execdriver/native
File: init.go@35

---
4: Init
Package: github.com/docker/docker/pkg/reexec
File: reexec.go@26

---
5: main
Package: main
File: docker.go@18

---
6: main
Package: runtime
File: proc.go@63

---
7: goexit
Package runtime
File: asm_amd64.s@2232
Error response from daemon: Cannot start container <id>: [8] System error: state /system.slice/docker.service: no such file or directory

Output of docker version:

Client/Server:
 Version: 1.9.0
 API version 1.21
 Go version: go1.4.2
 Git commit: 76d6bc9
 OS/Arch: linux/amd64

Some additional info:
Kernel version: 3.10.0-123.el7.x86_64
OS: CentOS Linux 7 (Core)
Storage Driver: devicemapper

Any clue as to why this happened? It seems very out of the blue as this is the first we've seen this issue. I've seen similar on the internet, but none reference this specific file.

Thanks.

@HackToday
Copy link
Contributor

is it possible for you to check with Marathon guys first, if it is a docker issue ?

@thaJeztah
Copy link
Member

Can you try configuring docker to use cgroupfs instead of systemd for cgroups? We changed to cgroupfs as a default in #17704, because systemd cgroups have a lot of issues, including systemd doing really weird things #20633

You can switch to using cgroupfs by adding --exec-opt native.cgroupdriver=cgroupfs to your daemon options

nathansamson added a commit to nathansamson/deis that referenced this issue Jul 23, 2016
The (CorOS) default of systemd might have some problems.
See also coreos/bugs#1435
moby/moby#21444 and
moby/moby#21678
nathansamson added a commit to nathansamson/deis that referenced this issue Jul 25, 2016
The (CorOS) default of systemd might have some problems.
See also coreos/bugs#1435
moby/moby#21444 and
moby/moby#21678
aj-may pushed a commit to Hearst-Hatchery/deis that referenced this issue Sep 15, 2016
The (CorOS) default of systemd might have some problems.
See also coreos/bugs#1435
moby/moby#21444 and
moby/moby#21678
@thaJeztah
Copy link
Member

closing because this went stale, and the default is now cgroupfs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants