Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
`docker-compose build` is saying that I'm out of memory, but `docker build .` works fine? #3775
Bad title. Out of storage space, not memory. My bad!
It's a 10.4gb container, too.
My free space:
Example error output:
So what ended up happening to me was:
Another weird thing, when
Edit: I think that the storage space it's referring to is my memory.
I did a
Okay so, update on this issue:
Previously, docker-compose seemed to be running perfectly fine with larger images. After rebuilding my
Adding a $TMPDIR variable pointing to a disk-based filesystem completely resolved my issue, which leads me to believe that
What made it stop?
@kminehart When you run
I hope that clarifies things!
Right, @shin-, that's eventually what I figured out.
I'm curious why this wasn't happening before, though, even though my
Or maybe I'm just being ridiculous and my image size increased significantly and I'm just misassociating two things.
Okay, that makes a lot of sense.
I had a MySQL container with a mounted directory for
Does Docker Compose's build context include everything in the directory that docker-compose.yml? Or is this the use-case where I should be including a .dockerignore?