Docker compose "--no-build was passed"

Question

When I try to docker-compose up with one of my images missing, I get:

Service 'server' needs to be built, but --no-build was passed.

I understand from the documentation that this is indeed what the --no-build option does:

--no-build Don't build an image, even if it's missing

Why is this default behavior and how can my docker-compose up automatically trigger a docker-compose build beforehand?

VonC · Accepted Answer · 2015-08-18 08:23:48Z

2

This is monitored by issue 1679: "docker-compose up assumes --no-build"

The crux of the problem is:

if my image exists (because I ran docker-compose build before), but the referred Dockefile changes, up won't trigger an automatic rebuild?
It may be a misunderstanding, but I thought that up always rebuilds the image if the Dockerfile is out of sync with the image, unless --no-build is passed.

aanand adds:

up only checks that the image exists, not that it's up-to-date.
There's actually no way to check that.

We've discussed alternative approaches, including always building and never building.

edited Aug 18, 2015 at 8:23

answered Aug 16, 2015 at 13:19

VonC

1.4m568 gold badges4.8k silver badges5.7k bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

Marc Perrin-Pelletier Over a year ago

Ok thanks! I'll follow up on that thread. I'm wondering though why there isn't simply a --force-build option just like there's a --force-recreate option (reference)..

Collectives™ on Stack Overflow

Docker compose "--no-build was passed"

1 Answer 1

1 Comment

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

1 Comment

Related