Docker Community Forums

Share and learn in the Docker community.

Can not fork: error can not allocate memory

(Anthony R. Colombo) #1


I am running a process that is not copying super large files within a docker container, however I am getting memory leak errors of “error can not fork:can not allocate memory”. This could be a result of numerous things within my docker container. however, I wish to investigate whether or not it has to do with memory.

here is my docker debug info which shows my memory useage.

basespace@ubuntu:/$ sudo docker --debug info
Containers: 7
Images: 80
Storage Driver: devicemapper
Pool Name: docker-8:1-1844209-pool
Pool Blocksize: 65.54 kB
Backing Filesystem: extfs
Data file: /dev/loop0
Metadata file: /dev/loop1
Data Space Used: 9.228 GB
Data Space Total: 107.4 GB
Metadata Space Used: 9.961 MB
Metadata Space Total: 2.147 GB
Udev Sync Supported: false
Data loop file: /var/lib/docker/devicemapper/devicemapper/data
Metadata loop file: /var/lib/docker/devicemapper/devicemapper/metadata
Library Version: 1.02.82-git (2013-10-04)
Execution Driver: native-0.2
Kernel Version: 4.1.0-040100rc2-generic
Operating System: Ubuntu 14.04.2 LTS
CPUs: 1
Total Memory: 1.954 GiB
Name: ubuntu
Debug mode (server): false
Debug mode (client): true
Fds: 12
Goroutines: 16
EventsListeners: 0
Init Path: /usr/bin/docker
Docker Root Dir: /var/lib/docker
Username: arcolombo
Registry: []
WARNING: No swap limit support

I do notice quite a bit of cyberspace date used. Advice? What is the data limits? I have deleted most of my docker containers, and untagged many of my unused images.

My system has plenty of storage

asespace@ubuntu:/$ df -h
Filesystem Size Used Avail Use% Mounted on
/dev/sda1 61G 11G 47G 19% /
none 4.0K 0 4.0K 0% /sys/fs/cgroup
udev 990M 4.0K 990M 1% /dev
tmpfs 201M 448K 200M 1% /run
none 5.0M 0 5.0M 0% /run/lock
none 1001M 4.0K 1001M 1% /run/shm
none 100M 0 100M 0% /run/user

i am just inquiring if my docker memory space is an issue.thank you