ARM images appear to be missing from quay.io

[jbalonso]

After all the hard work in #95 and #96 , I'm seeing the following when I run docker manifest inspect quay.io/external_storage/local-volume-provisioner:v2.3.3:

{
   "schemaVersion": 2,
   "mediaType": "application/vnd.docker.distribution.manifest.list.v2+json",
   "manifests": [
      {
         "mediaType": "application/vnd.docker.distribution.manifest.v2+json",
         "size": 1160,
         "digest": "sha256:038b1d9c8ded10aa1f4720802fdae6f0cceaaecbb5fe964c2b7294e47a769c6e",
         "platform": {
            "architecture": "amd64",
            "os": "linux"
         }
      }
   ]
}

Also, I'm getting ErrImagePull on my arm64 kubelet.

[msau42]

Unfortunately, our underlying release-infra does not support cross building, so we had to disable it: #140

[cofyc]

Sorry about this. As a workaround, you can build arm images for your own use in the following steps for now:

1. create a docker repository, e.g. quay.io/jbalonso/local-volume-provisioner

2. build image (docker is required)

cd $GOPATH/src/sigs.k8s.io/sig-storage-local-static-provisioner
make provisioner REGISTRY=quay.io/jbalonso VERSION=canary ARCH=arm
make provisioner REGISTRY=quay.io/jbalonso VERSION=canary ARCH=arm64

3. push image

docker push quay.io/jbalonso/local-volume-provisioner:arm
docker push quay.io/jbalonso/local-volume-provisioner:arm64

[jbalonso]

Thanks. This got away from me for a bit.

My use case required multi-arch image manifests, but I was able to get hack/release.sh to work for me with a manual hack to set ALL_ARCH (perhaps letting that be overridden by an environment variable would be cool?).

I've since found that rancher/local-path-provisioner is a better fit for my use case. That said, it is my suspicion that the community might be served to have this issue as a reminder that multi-arch (including arm) images are desirable but lacking. As such, I leave the question with you whether this issue should stay open.

[cofyc]

perhaps letting that be overridden by an environment variable would be

cool? Good idea! Can you open a PR for this? This issue can be kept open until we support multi-arch again.

On Sat, Nov 2, 2019 at 9:16 AM Jason B. Alonso ***@***.***> wrote: Thanks. This got away from me for a bit. My use case required multi-arch image manifests, but I was able to get hack/release.sh to work for me with a manual hack to set ALL_ARCH (perhaps letting that be overridden by an environment variable would be cool?). I've since found that rancher/local-path-provisioner <https://github.com/rancher/local-path-provisioner> is a better fit for my use case. That said, it is my *suspicion* that the community might be served to have this issue as a reminder that multi-arch (including arm) images are desirable but lacking, as such, I leave the question with you whether this issue should stay open. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#153?email_source=notifications&email_token=AAAWMUWPTUDVYCO6FSVIVWDQRTIHTA5CNFSM4JGAMQWKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEC4QK7A#issuecomment-548996476>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAWMUVTLDJSKX36ZKMXEJDQRTIHTANCNFSM4JGAMQWA> .

-- Yecheng Fu (Cofyc) https://yechengfu.com

[jbalonso]

Ok. I've submitted my PR for the override capability. It includes a touch of documentation--I felt bold enough to give it as a third invocation example.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[cofyc]

/remove-lifecycle stale

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[cofyc]

/remove-lifecycle stale

[msau42]

in the csi project, we're currently migrating our build infra from quay to gcr provided by k8s-infra. One of the goal is to support multi-arch images using docker buildx. So far experimentation is going well, and we may want to consider something similar for this repo. example: https://github.com/kubernetes-csi/node-driver-registrar/blob/master/cloudbuild.yaml

[zhlhahaha]

Hi @cofyc
as cleanup_binfmt_misc() has removed from prow bootstrap.
kubernetes/test-infra#14768

Can we re-enable cross build for multi-platform image?

[cofyc]

hi, @msau42 is it ready to add a cloud build configuration to support multi-arch images now?

[msau42]

Yes, we actually just created a new image repo for all sig-storage sponsored projects: kubernetes/k8s.io#943

[cofyc]

/assign
Great!