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

[regression] apachesuperset.docker.scarf.sh/apache/superset:latest-dev no longer contains images for arm64 #26822

Closed
3 tasks done
CatStudioApp opened this issue Jan 27, 2024 · 5 comments
Assignees

Comments

@CatStudioApp
Copy link

Bug description

About one week ago, I can download arm64 images from apachesuperset.docker.scarf.sh/apache/superset

However, right now it does not support arm64 anymore.

How to reproduce the bug

$ docker pull apachesuperset.docker.scarf.sh/apache/superset:latest
latest: Pulling from apache/superset
no matching manifest for linux/arm64/v8 in the manifest list entries

Screenshots/recordings

No response

Superset version

master / latest-dev

Python version

Not applicable

Node version

Not applicable

Browser

Not applicable

Additional context

No response

Checklist

  • I have searched Superset docs and Slack and didn't find a solution to my problem.
  • I have searched the GitHub issue tracker and didn't find a similar bug report.
  • I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section.
@kakoni
Copy link
Contributor

kakoni commented Jan 31, 2024

@CatStudioApp The quick fix as per #25434 is to do export DOCKER_DEFAULT_PLATFORM=linux/amd64

@mistercrunch
Copy link
Member

Suffixing -arm should work as in latest-arm, documented changes here #26923

@mistercrunch
Copy link
Member

But I don't have the creds to push to docker from local so I can't retag stuff, or I'd have to trick CI into it.

@rusackas
Copy link
Member

I believe all these ARM issues were solved by @mistercrunch after this ticket was last touched. I'll optimistically close it, but let us know if you're still facing this (and perhaps some updated context) and we can certainly revisit/reopen.

@mistercrunch
Copy link
Member

Yup we should be good, there was a bit of a long tail of issues around older versions that were cut off master before some of the work took place. Everything should be ironed out now.

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

4 participants