-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Try to use old mamba version #1545
Try to use old mamba version #1545
Conversation
My approach should work, but we have a much bigger problem. https://github.com/jupyter/docker-stacks/runs/4493047317?check_suite_focus=true#step:7:4475
Because we build so many images, they take too much space and we end up pulling images from dockerhub. |
@consideRatio I will for now completely disable arm images building at all :( I will try to increase the volume using GitHub action for that, but I do think it's a fragile approach as well. |
Nice, the only |
That sounds reasonable. Given the limited maintenance capacity we have, and that this blocks everything if not maintained, cutting away something to save something else seems reasonable. I think this strategy hasn't been robust enough given that each failure cause a lot of additional work and is hard to resolve due to the monolith CI jobs. I consider a resolution towards having arm again after disabling it would be to put in more work in making the CI system work in a more composable manner (#1407), I think that would make it handle multiple architectures in a more maintenance sustainable way. Are you making some last attempts to get things to work atm? |
Yes, let's wait for the latest build - it should run faster (because caching images works) and it gives expected result (because of caching). |
Finally, this seems to work. |
@mathbunnyru it worked! You are amazing! Thank you for your thorough work!!! ❤️ 🎉 |
No description provided.