Rui Yang

Hi, thx reporting this bug. After some investigation, these are what I found: 1. concourse itself is fine since it is replying on the check response from each individual resource...

It seems like it is a desired response from `check` script based on the discussion we have at retros. Though I think it is still a bit un-clear on resource...

Hi, in general Github issues is not a good fit for asking questions. It should be used to track problems and features. I would suggest [concourse forum](https://discuss.concourse-ci.org/) and [community on...

My knowledge with git shallow clone is limited. Would adding this flag cause users cloning more data than they want (if their submodules is meant to be shallow)?

Could you provide simple steps to reproducte it? From the code here it will try the ping with both http and https https://github.com/concourse/docker-image-resource/blob/770ff365918ed0d2d0f838b2e4b2bed40cc86d80/cmd/check/main.go#L208 if any attemp works the registry URL...

the job that builds the image is here `https://ci.concourse-ci.org/teams/main/pipelines/concourse/jobs/build-golang-builder-image/` we don't have plan for arm64 support yet.

Actually we are deprecating this resource in favor of https://github.com/concourse/registry-image-resource and we'd love to adding arm64 support there.

@odidev sounds like you have already built a golang-builder-image in arm64. You could then fork the registry-image-resource to build the resource image to support arm64. Is there anything else blocking...

Blocked by https://github.com/moby/moby/issues/30880

Please make sure your dockerfile is able to run with a `docker build` first. Otherwise you could post your dockerfile here if you are still having this problem. Thx.