Concourse 8.x docker-image resource types fail with "failed to fetch manifest"
search cancel

Concourse 8.x docker-image resource types fail with "failed to fetch manifest"

book

Article ID: 437342

calendar_today

Updated On:

Products

Concourse for VMware Tanzu

Issue/Introduction

When using Concourse 8.x, using a resource with the resource type "docker-image" fails to check with the following error:

failed to fetch manifest: Head "https://registry-1.docker.io/v2/pivotalcf/pivnet-resource/manifests/latest": denied: <!DOCTYPE html><html lang="en-US"><head><title>Just a moment...</title>*{box-sizing:border-box;margin:0;padding:0}html

An example of a resource that faces this issue:

---
resources:
- name: pivnet-resource
  type: registry-image
  check_every: 24h
  source:
    repository: pivotalcf/pivnet-resource
    tag: latest

Environment

Concourse 8.x

Resolution

Changing the resource type to use registry-image instead of docker image resolves the issue. Using the above example:

---
resources:
- name: pivnet-resource
  type: registry-image
  check_every: 24h
  source:
    repository: pivotalcf/pivnet-resource
    tag: latest

registry-image resource was developed as a replacement for docker-image:

https://github.com/concourse/registry-image-resource

It is recommended to update your resource type to registry-image to avoid any issue.

Powered by Wolken Software