Issue with the apache/superset:dockerize

[rnpaiva]

Bug description

Kubernetes can't pull the image apache/superset:dockerize . I tested in my local and it's not possible as well .

How to reproduce the bug

docker pull apache/superset:dockerize

Screenshots/recordings

Superset version

3.0.3

Python version

3.9

Node version

16

Browser

Chrome

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.

[mistercrunch]

Fix is getting crafted here -> #26787

[kamilrotter]

Hey @mistercrunch , we can't pull image using tag 'latest', is that the same issue?

[mistercrunch]

Yes should be the same, we had conflicting tags before that just happened to make the amd builds get the proper base docker tags because they were running sequentially with amd last. Now that we parallelize the build, and because arm is emulated and slower, it tends to take over the tags. Now I'm adding suffixes to all arm builds so that tags won't conflict.

[jun0tpyrc]

or do docker multi-arch build to make things work implicitly...
most other images in chart are amd64 only

[jun0tpyrc]

or may do docker multi-arch build to make things work implicitly...
most other images in chart are amd64 only

[kevin-delisle-peakpower]

or may do docker multi-arch build to make things work implicitly... most other images in chart are amd64 only

This is the right way of dealing with this. Modifying your build to assemble a multi-arch image means no one has to worry about pulling alternate tags to get the build that's right for them, and it avoids adding complexity to the tagging structure.

[rnpaiva]

it's happening again

[rnpaiva]

do you have the dockerfile please ? I'll compile and push in my ECR

[kevin-delisle-peakpower]

@rnpaiva As a workaround, I pinned my dependencies to a specific release instead of using the dockerize image.
If you browse Docker Hub, there's a bunch of tags that look like apache/superset:<commit-hash>-dockerize-linux-amd64-<base-image-version>: https://hub.docker.com/r/apache/superset/tags?page=1&name=docker

(ex. e6f9ef159d113f9cf698791e5f965855e7be0169-dockerize-linux-amd64-3.9-slim-bookworm)

[edu-sistec]

Hello, kevin-delisle-peakpower
I have problems booting in docker, I think it's also due to the AMR64 architecture.

As you say there are these options but I have tried some and I get errors.

I don't understand if the error is the image that is wrong, or the missing file 'config.json' if I should create it, but there is no information about where this file 'config.json' should be located , nor that it has to be introduced.

Have you been able to run some of these images? Which ones exactly? Did you have to do anything special?

Thanks

[kevin-delisle-peakpower]

@edu-sistec I used the apache/superset:b0c8f620d6517b400a9676c01393cda8a57b0d64-dockerize-linux-amd64-3.9-slim-bookworm image, in particular.
I only used it for the initImage portion of the Helm chart when I installed it, since that was what I was running into problems with. We're still using a tagged release for the "main" container instance of the installation.

I'm not versed in the use of Superset's docker-compose install, but if there's a section that's meant to run the postgres initialization, that's probably where you'd want to use this image.

[mistercrunch]

Ok i merged that PR, eventually should get a apache/superset:dockerize-latest to point to as we push the next release

[edu-sistec]

Hello kevin-delisle-peakpower

Hello,

I am now seeing that you are booting the amd64 image.
I used your comments to try to boot the arm64 image, because I'm on an arm64 architecture.
I get these errors, I attach an image
Am I doing something wrong in docker-compose?

Thank you so much

[mistercrunch]

no bash!?

[mistercrunch]

I don't really use docker here on my local setup and it looks like it's busted for my new mac (linux/arm64/v8), can't really help. I really like docker conceptually but in practice it's a different story.

[jun0tpyrc]

for those who using helm install and want a quick workaround with min changes , that place in helm values to temp modify before there is a tag for default initImage that does multi-arch in auto

 initImage:
   repository: apache/superset
-  tag: dockerize
+  tag: ea6cbcef3e980e42d3a19b8fc5928f973fd7be4a-dockerize-linux-amd64-3.9-slim-bookworm # NOTE: https://github.com/apache/superset/issues/26788
   pullPolicy: IfNotPresent

[edu-sistec]

Hello jun0tpyrc,

I tried to do what you say (I attach image 1) but still it want to take the standard Superset image.
I have also put in the docker-compse file the image I would like to use (I attach image 2), and it keeps saying that it cannot run the 'bach'.
Is there something I'm not doing right?

thank you so much,
Edu

[arundh93]

Any update on this issue?

[mistercrunch]

This should help #27055