pull --ignore-pull-failures does not ignore failures since docker 1.13

[mishas]

To reproduce:

Create a docker-compose.yml file with the following content:

version: '2'

services:
    my_service:
        build:
            context: .
            dockerfile: Dockerfile
        image: my/image

Running docker-compose pull --ignore-pull-failures prints out the expected ERROR output (
ERROR: b'repository my/image not found: does not exist or no pull access'),
And returns the unexpected 1 status code :(.

This worked well in versions 1.12.x, but stopped working once updated to 1.13

[williamboman]

I upgraded docker-compose from 1.8.0 to 1.10.0, seems to have fixed it. Unsure which docker version I was on though.

[komuw]

I'm also getting a similar error but mine is for the general case, where docker-compose up or the other commands like pull do not work.
I've opened a fresh issue with more info #4385

[adamdicarlo]

This is still broken in docker-compose version 1.14.0, build c7bdf9e

Doesn't pull all it can, and exits with error.

[SinErgy84]

@adamdicarlo can also confirm in Docker version 17.05.0-ce, build 89658be --> broken

[atcol]

This still fails on docker-compose version 1.8.0, build f3628c7

[atcol]

Confirmed works on docker-compose version 1.17.0-rc1, build a0f95af

[Tb0]

This still fails on docker-compose version 1.23.1, build b02f1306 AFAIK.

[Tb0]

ignore-pull-failures still doesn't work on docker-compose version 1.23.2, build 1110ad01

@shin- Can you maybe have a quick look at this please?

[Tb0]

I found a way to get to work --ignore-pull-failures option.

Your command should be:
docker-compose pull --ignore-pull-failures || true

Hope this will help anyone with this issue.
Cheers!

[morgangalpin]

@Tb0 That does not make --ignore-pull-failures work. It just makes the script that calls docker-compose pull --ignore-pull-failures || true not fail. The docker-compose pull --ignore-pull-failures command still terminates upon the first pull failure.

[stale]

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.

[stale]

This issue has been automatically closed because it had not recent activity during the stale period.

[lkdmid]

This is still an issue (latest everything).