Skip to content
This repository has been archived by the owner on Mar 20, 2023. It is now read-only.

Error when creating a pool in 3.5.0b3 #215

Closed
ausdjt opened this issue Jun 24, 2018 · 3 comments
Closed

Error when creating a pool in 3.5.0b3 #215

ausdjt opened this issue Jun 24, 2018 · 3 comments

Comments

@ausdjt
Copy link

ausdjt commented Jun 24, 2018

2018-06-24T22:04:51,251644358+00:00 - DEBUG - Pulling Docker Image: alfpark/batch-shipyard:3.5.0b3-cascade
2018-06-24T22:04:53,045645169+00:00 - ERROR - Error response from daemon: Get https://registry-1.docker.io/v2/alfpark/batch-shipyard/manifests/3.5.0b3-cascade: error parsing HTTP 404 response body: invalid character ':' after top-level value: "404: Page Not Found"

@ausdjt
Copy link
Author

ausdjt commented Jun 24, 2018

And now this:

2018-06-24T22:20:49,645550900+00:00 - DEBUG - Pulling Docker Image: alfpark/blobxfer:1.2.1
2018-06-24T22:20:51,841218698+00:00 - ERROR - Error response from daemon: Get https://registry-1.docker.io/v2/alfpark/blobxfer/manifests/1.2.1: received unexpected HTTP status: 503 Service Unavailable

@alfpark
Copy link
Collaborator

alfpark commented Jun 25, 2018

It looks like Docker Hub was down/degraded during that time period.

I'll formalize a backlog item to have an alternate registry that users can specify to failover for Batch Shipyard critical images.

@alfpark
Copy link
Collaborator

alfpark commented Jun 25, 2018

Tentatively scheduled a feature to address this for inclusion in 3.5.0 final.

@alfpark alfpark closed this as completed Jun 25, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants