https://bugzilla.redhat.com/show_bug.cgi?id=1216096
Bug ID: 1216096
Summary: Hard coded /tmp size of 64M causes problems
Product: Fedora
Version: 21
Component: docker-io
Keywords: Extras
Assignee: ichavero(a)redhat.com
Reporter: agoldste(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: adimania(a)gmail.com, admiller(a)redhat.com,
agoldste(a)redhat.com, eparis(a)redhat.com,
golang(a)lists.fedoraproject.org, hushan.jia(a)gmail.com,
ichavero(a)redhat.com, jchaloup(a)redhat.com,
jperrin(a)centos.org, lsm5(a)redhat.com, lsu(a)redhat.com,
mattdm(a)redhat.com, mgoldman(a)redhat.com,
miminar(a)redhat.com, s(a)shk.io, thrcka(a)redhat.com,
vbatts(a)redhat.com
Depends On: 1215768
+++ This bug was initially created as a clone of Bug #1215768 +++
I'm looking at b482aff8fbb5dc59d25335b67353465071d6bd45 in rhatdan/docker
It seems that you are hode coding all tmpfs mounts to 64M. Docker previously
mounted tmpfs at /tmp and this added /run.
Golang uses TMPDIR to do its builds. When doing a rather large build (like
openshift) which is larger than 64M it obviously can not work!
I think this size needs to be somehow configurable... Deciding that X is
enough /tmp space for everyone just doesn't seem like a possibility...
--- Additional comment from Daniel Walsh on 2015-04-28 08:13:12 EDT ---
Eric, any chance of changing TMPDIR -> /var/tmp?
--- Additional comment from Daniel Walsh on 2015-04-28 08:15:46 EDT ---
This should also not be happening in a docker build?
--- Additional comment from Daniel Walsh on 2015-04-28 08:32:57 EDT ---
Removed the size restrictions on /tmp and /run
Lokesh we need a new build of docker-1.6
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1215768
[Bug 1215768] Hard coded /tmp size of 64M causes problems
--
You are receiving this mail because:
You are on the CC list for the bug.