Skip to content

Does proxy work on unavailable upstream? #141

@Felixoid

Description

@Felixoid

Hello. According to manual, the registry mirror requests if the images updated on the ustream.

We use docker very intensively in our CI, and quite often affected by issues like this:

Exception: Command ['docker-compose', '--env-file', '/ClickHouse/tests/integration/test_cleanup_dir_after_bad_zk_conn/_instances_0/.env', '--project-name', 'roottestcleanupdirafterbadzkconn', '--file', '/ClickHouse/tests/integration/test_cleanup_dir_after_bad_zk_conn/_instances_0/node1/docker-compose.yml', '--file', '/compose/docker_compose_keeper.yml', 'pull'] return non-zero code 1: Pulling zoo2  ... 
Pulling zoo3  ... 
Pulling zoo1  ... 
Pulling node1 ... 
Pulling zoo3  ... error
Pulling zoo1  ... error
Pulling zoo2  ... error
Pulling node1 ... error

ERROR: for zoo3  Get "https://registry-1.docker.io/v2/": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)

ERROR: for zoo1  Get "https://registry-1.docker.io/v2/": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)

ERROR: for zoo2  Get "https://registry-1.docker.io/v2/": context deadline exceeded

ERROR: for node1  Get "https://registry-1.docker.io/v2/": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
Get "https://registry-1.docker.io/v2/": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
Get "https://registry-1.docker.io/v2/": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
Get "https://registry-1.docker.io/v2/": context deadline exceeded
Get "https://registry-1.docker.io/v2/": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)

And then a huge number of jobs fail.

Do I understand correctly, that registry:2 can't be setup to serve requests with what it has w/o failing?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions