Compose: pull requires valid build path

[tanmayambre]

docker-compose version
docker-compose version 1.7.0, build 0d7bf73
docker-py version: 1.8.0
CPython version: 2.7.9
OpenSSL version: OpenSSL 1.0.1e 11 Feb 2013

I have a docker-compose file

version: '2'
services:
    xyzservice:
    image: xxx-image
    container_name: xxx_container
    build:
      context: ./somecontext
      dockerfile: Dockerfile.xxx
    networks:
      - some-network

When I want to build the image using docker-compose build, I understand that the _Dockerfile.xxx_ is absolutely required.

But if I just want to pull the image using docker-compose pull why is the Dockerfile.xxx required?

I get the following error on pull command

ERROR: build path ./somecontext either does not exist, is not accessible, or is not a valid URL.

[shin-]

You don't need the build section if you're just going to pull the image. Your compose file should be

version: '2'
services:
    xyzservice:
    image: xxx-image
    container_name: xxx_container
    networks:
      - some-network

[tanmayambre]

Thanks,
My scenario is the developer requires the buildpath to build & push the container while if someone wants to just run the container without build just pulling mage using same compose file.

[fvanderbiest]

This issue is annoying for our use case where the compose file is used both to build and run the app. Valid build paths should not be required to run docker-compose pull IMO.

[Elyytscha]

this is annoying, just saying

[zypA13510]

Are you sure this is kind/question? @docker/maintainer

As noted by @fvanderbiest and other people, there are valid use cases where pulling without building is required. Could you please consider this as an enhancement?

[yamac-kurtulus]

This is seriously annoying and makes no sense. Could you please implement this?

[nojvek]

Just hit this, this is really annoying indeed.

My usecase is I want to build from github actions and push to registry on PR commit. When merged to master a separate job ssh into a digital ocean $5 pod and does docker-compose pull and docker-compose restart to pick up the latest changes.

This feels like a serious limitation. Why would someone need to rebuild if they can just pull ? 🤷‍♂

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[Elyytscha]

its not stale its still annoying

[stale[bot]]

This issue has been automatically marked as not stale anymore due to the recent activity.

[MartinSunal]

it seems to be fixed in #7564

[Elyytscha]

yep its fixed with 1.27.0, thanks alot! could be closed now i think