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.

Sign up for GitHub

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

Jump to bottom

Containers fail to start when using --memory in docker 17.06.1-ce #34616

Closed
TimWolla opened this issue Aug 23, 2017 · 3 comments
Closed

Containers fail to start when using --memory in docker 17.06.1-ce #34616

TimWolla opened this issue Aug 23, 2017 · 3 comments
Labels
area/runtime version/17.06

Comments

@TimWolla
Copy link
Contributor

TimWolla commented Aug 23, 2017 •
edited
Loading

Description

After I upgraded Docker from 17.06.0~ce-0~debian to 17.06.1~ce-0~debian containers fail to start with --memory set.

Steps to reproduce the issue:

  1. docker run -it --rm --memory 1G debian bash

Describe the results you received:

docker: Error response from daemon: oci runtime error: container_linux.go:262: starting container process caused "process_linux.go:261: applying cgroup configuration for process caused \"No such device or address\"".

Describe the results you expected:
A bash running inside a Debian container.

Additional information you deem important (e.g. issue happens only occasionally):
Happens even after a reboot of the complete machine.

Output of docker version:

Client:
 Version:      17.06.1-ce
 API version:  1.30
 Go version:   go1.8.3
 Git commit:   874a737
 Built:        Thu Aug 17 22:01:59 2017
 OS/Arch:      linux/amd64

Server:
 Version:      17.06.1-ce
 API version:  1.30 (minimum version 1.12)
 Go version:   go1.8.3
 Git commit:   874a737
 Built:        Thu Aug 17 21:59:51 2017
 OS/Arch:      linux/amd64
 Experimental: false

Output of docker info:

Containers: 22
 Running: 22
 Paused: 0
 Stopped: 0
Images: 139
Server Version: 17.06.1-ce
Storage Driver: zfs
 Zpool: rpool
 Zpool Health: ONLINE
 Parent Dataset: rpool/docker
 Space Used By Parent: 2966364160
 Space Available: 774392807424
 Parent Quota: no
 Compression: on
Logging Driver: json-file
Cgroup Driver: systemd
Plugins: 
 Volume: local
 Network: bridge host macvlan null overlay
 Log: awslogs fluentd gcplogs gelf journald json-file logentries splunk syslog
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 6e23458c129b551d5c9871e5174f6b1b7f6d1170
runc version: 810190ceaa507aa2727d7ae6f4790c76ec150bd2
init version: 949e6fa
Security Options:
 apparmor
 seccomp
  Profile: default
Kernel Version: 4.9.0-3-amd64
Operating System: Debian GNU/Linux 9 (stretch)
OSType: linux
Architecture: x86_64
CPUs: 8
Total Memory: 15.57GiB
Name: *
ID: *
Docker Root Dir: /docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
Experimental: false
Insecure Registries:
 127.0.0.0/8
Live Restore Enabled: true

Additional environment details (AWS, VirtualBox, physical, etc.):
Dedicated bare metal host running Debian Stretch.
@yummypeng
Copy link
Contributor

yummypeng commented Aug 24, 2017 •
edited
Loading

docker keeps failing when I use --memory:

# docker run -it --rm --memory 50M ubuntu bash
docker: Error response from daemon: oci runtime error: container_linux.go:262: starting container process caused "process_linux.go:339: container init caused \"\"".

If I try to use a larger memory, the error becomes more detailed:

# docker run -it --rm --memory 100M ubuntu bash
docker: Error response from daemon: oci runtime error: container_linux.go:262: starting container process caused "process_linux.go:339: container init caused \"read init-p: connection reset by peer\"".

Seems a runc issue.

I tried with the latest docker:

# docker version
Client:
 Version:      unknown-version
 API version:  1.30
 Go version:   go1.7.5
 Git commit:   3dfb834
 Built:        Tue Aug  8 07:32:55 2017
 OS/Arch:      linux/amd64

Server:
 Version:      17.06.0-dev
 API version:  1.32 (minimum version 1.12)
 Go version:   go1.8.1
 Git commit:   ff167a285
 Built:        Thu Aug 24 11:45:17 2017
 OS/Arch:      linux/amd64
 Experimental: false
# docker-runc -v
runc version 1.0.0-rc3
commit: 2d41c047c83e09a6d61d464906feb2a2f3c52aa4
spec: 1.0.0-rc5

@tonistiigi
Copy link
Member

cc @tiborvass

@TimWolla
Copy link
Contributor Author

Seems to be working again as of Docker 17.07

@TimWolla TimWolla mentioned this issue Oct 7, 2017
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/runtime version/17.06
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@TimWolla @tonistiigi @GordonTheTurtle @yummypeng