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

Z2JH on Raspberry PI Cluster exec format error on pre puller #2253

Closed
JamesCarscadden opened this issue Jun 16, 2021 · 7 comments
Closed

Z2JH on Raspberry PI Cluster exec format error on pre puller #2253

JamesCarscadden opened this issue Jun 16, 2021 · 7 comments
Labels

Comments

@JamesCarscadden
Copy link

JamesCarscadden commented Jun 16, 2021

Bug description

I am attempting to set up the Z2JH chart on a Raspberry PI (arm64) based cluster and am encountering some problems with the pre Puller job/pods. Specifically we get an exec format error (unsurprising since that container does not appear to have an arm64 version.

Expected behaviour

These containers should have arm64 versions

Actual behaviour

exec format error due to no arm64 version

How to reproduce

Use base Z2JH chart (v1.0.0) on an arm64 based cluster node

Your personal set up

Kubernetes v1.21.1 running on Raspberry PI 4 (8Gb) 4 node cluster.
Base OS is current version of Raspbian arm64 distribution
Using Helm to deploy the jupyterhub chart from https://jupyterhub.github.io/helm-chart/

This issue can be worked around by setting

prePuller:
    hook:
      enabled: false
    continuous:
      enabled: false

in the helm values

@welcome
Copy link

welcome bot commented Jun 16, 2021

Thank you for opening your first issue in this project! Engagement like this is essential for open source projects! 🤗

If you haven't done so already, check out Jupyter's Code of Conduct. Also, please try to follow the issue template as it helps other other community members to contribute more effectively.
welcome
You can meet the other Jovyans by joining our Discourse forum. There is also an intro thread there where you can stop by and say Hi! 👋

Welcome to the Jupyter community! 🎉

@manics
Copy link
Member

manics commented Jun 16, 2021

I suspect the problem is that


isn't multi-arch.

@JamesCarscadden
Copy link
Author

JamesCarscadden commented Jun 16, 2021

I don't believe the image-awaiter is the actual problem in this case -- looking closer at the logs the initial problem (if I remove the values configuration mentioned in the issue), is that the 'hook-image-puller' pod fails with 'exec format error' actually on 'image-pull-singleuser' init container (which is probably related to #2145.)

If I add

  prePuller:
    hook:
      enabled: false

to my values, then I encounter the same problem with 'continuous-image-puller' pod. And then finally if I also add the continuous->enabled->false as well then I get past this problem onto other issues. So that's my bad for not looking at this as closely as I should have. Likely this can be considered a duplicate of #2145

@JamesCarscadden
Copy link
Author

My initial bug report I made the assumption that since the values were 'prePuller' related, that the exec format error was related to the jupyterhub/k8s-pre-puller container, but that doesn't actually appear to be used anymore. Sorry.

@manics
Copy link
Member

manics commented Jun 17, 2021

That would explain it, the default singleuser image doesn't support ARM64. Shall we close this? There's been a fair bit of activity on jupyter/docker-stacks#1019 and linked PRs so hopefully it won't be too long, in the meantime you can find some alternative ARM64 builds in that thread.

@JamesCarscadden
Copy link
Author

Yup close it, I'll wait for #2145

@consideRatio
Copy link
Member

Closing as duplicate of #2145

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants