raspbernetes/multi-arch-images

Silly Question, how to pull images correctly for Rook operator.yaml

matthew-williams opened this issue · 4 comments

matthew-williams commented

I am sure this is simple, but I cannot see any consistency between peoples operator.yaml file and how to use the images you provide in mine.

Per this issue: rook/rook#5799

He goes from quay.io/k8scsi/csi-attacher which totally resolves to a repo in my browser to docker.io/madhupr001/csi-attacher which does not but according to his comments thats not his issue (it's unrelated to his format of the url).

Now it looks like everything is supposed to be URL encoded for these ENV's but I have tried many versions for yours and cannot get anything except an image pull back off error.

I have tried the following formats:
raspbernetes/ceph-csi
hub.docker.com/raspbernetes/ceph-csi
docker.io/raspbernetes/ceph-csi

My current chunk is below:

# (Optional) Allow starting unsupported ceph-csi image
  ROOK_CSI_ALLOW_UNSUPPORTED_VERSION: "false"
  # The default version of CSI supported by Rook will be started. To change the version
  # of the CSI driver to something other than what is officially supported, change
  # these images to the desired release of the CSI driver.
  ROOK_CSI_CEPH_IMAGE: "docker.io/raspbernetes/ceph-csi"
  ROOK_CSI_REGISTRAR_IMAGE: "docker.io/raspbernetes/csi-node-driver-registrar"
  ROOK_CSI_RESIZER_IMAGE: "docker.io/raspbernetes/csi-external-resizer"
  ROOK_CSI_PROVISIONER_IMAGE: "docker.io/raspbernetes/csi-external-provisioner"
  ROOK_CSI_SNAPSHOTTER_IMAGE: "docker.io/raspbernetes/csi-external-snapshotter"
  ROOK_CSI_ATTACHER_IMAGE: "docker.io/raspbernetes/csi-external-attacher"

Any help would be appreciated. I have looked for a few hours and have not found any operator.yaml files that reference your images directly.

Thank you!

issue-label-bot commented

Issue-Label Bot is automatically applying the label question to this issue, with a confidence of 0.88. Please mark this comment with 👍 or 👎 to give our bot feedback!

Links: app homepage, dashboard and code for this bot.

  • 👍1
xunholy commented

@matthew-williams not a silly question at all; I'm unfamiliar with the operator yaml you're referencing as I personally use OpenEBS, however, docker should be able to pull from the registry and with the following docker pull raspbernetes/ceph-csi:v3.1.0-arm64 which was an example directly from dockerhub.

With the other images do they work correctly as expected?

If you could provide your error here that would be perfect!

matthew-williams commented

So pulling that image with ROOK_CSI_CEPH_IMAGE: "raspbernetes/ceph-csi:v3.1.0-arm64" seems to work. Hoever the rest do not.

Following the same style:

  ROOK_CSI_CEPH_IMAGE: "raspbernetes/ceph-csi:v3.1.0-arm64"
  ROOK_CSI_REGISTRAR_IMAGE: "raspbernetes/csi-node-driver-registrar:2.0.0-arm64"
  ROOK_CSI_RESIZER_IMAGE: "raspbernetes/csi-external-resizer:latest-arm64"
  ROOK_CSI_PROVISIONER_IMAGE: "raspbernetes/csi-external-provisioner:2.0.0-arm64"
  ROOK_CSI_SNAPSHOTTER_IMAGE: "raspbernetes/csi-external-snapshotter:2.1.1-arm64"
  ROOK_CSI_ATTACHER_IMAGE: "raspbernetes/csi-external-attacher:3.0.0-arm64"

The rest just give an ImagePullBackOff error:
csi-rbdplugin-gp2hb 2/3 ImagePullBackOff 0

Which means I am likely not selecting the image correctly. I could not find an arm build for the other images such as csi-external-provisioner but if I do not specify -arm64 it pulls an amd64 image. How do I pull the arm image specifically?

xunholy commented

Please take a look at dockerhub to find the correct tags to use, these ones you're showing do not exist. there doesn't need to be a suffix -arm64.