Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue with the platform manifest for rook/ceph #2

Open
dalekurt opened this issue Jan 31, 2020 · 4 comments
Open

Issue with the platform manifest for rook/ceph #2

dalekurt opened this issue Jan 31, 2020 · 4 comments
Assignees

Comments

@dalekurt
Copy link

HI @danacr Thank you for you post. I would like to try Rook Ceph on my k3s cluster running on Raspberry Pi and I'm having an issue with the rook/ceph and I'm hoping you have solved it. When deploying the Docker image on my Raspberry Pi, I get the following error

failed to pull and unpack image "docker.io/rook/ceph:v1.0.6": failed to unpack image on snapshotter overlayfs: no match for platform in manifest

I found this issue rancher/k3s which is linked to a fix submitted by Rancher to containerd/containerd#3484

Model: Raspberry Pi 3 Model B Plus Rev 1.3
Processor model: ARMv7 Processor rev 4 (v7l)
OS: Raspbian Buster
K3S version: v1.17.0+k3s.1

@danacr
Copy link
Owner

danacr commented Feb 3, 2020

Have you tried downgrading your k3s version?

@serverbaboon
Copy link

I think you are trying to use to use an arm os and Rook/Ceph is only AMD64 and ARM64

@danacr I have posted some manifests to install a later version of Rook/Ceph than 1.06.
Let me know if you have any objections to this reference to your repo and you want me to remove or amend the reference.

Just for your reference really.

https://github.com/serverbaboon/rook-arm64

@danacr
Copy link
Owner

danacr commented Feb 17, 2020

Hi @serverbaboon, that is great to hear, I'll check them out and maybe I can update the version in the current tutorial. Feel free to link and share, I honestly don't mind :)

@serverbaboon
Copy link

serverbaboon commented Feb 18, 2020

Thinking about it I think you only need to checkout the common.yaml & oerator.yaml files, and not change your cluster and block yamls. I just wanted to use block mode rather than dir mounting.

The operator yaml file has some defaults for enabling utils ( its basically a tweaked version from the Rook repo) which you can probably tune out to save memory.

@danacr danacr self-assigned this Mar 9, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants