tanishqgandhi1908 opened a new issue, #8448: URL: https://github.com/apache/texera/issues/8448
Every computing unit runs the same image, fixed when the cluster is installed. Work needing a different Python version, a system package, or a library built from source cannot run — a Python virtual environment holds pip packages and nothing else. AlphaFold 3 fails all three ways at once. This lets an administrator register an image reference from a public registry. Texera checks it is a Texera computing-unit image and records the digest behind the reference. The image then appears in a dropdown when creating a computing unit; that unit runs it, and nobody else is affected. ### Design - Nothing is copied and no registry is added. Units pull the reference the same way the default computing-unit image is already pulled. - The reference is pinned to the digest resolved at registration, so a tag its owner moves later cannot change what runs. - Validation happens when the image is registered, in front of the administrator, not when a user's unit fails to start. - The image is chosen when a unit is created and fixed for its lifetime. **Out of scope:** building images, private registries, per-operator images. Design discussion: #7812 ### Sub-tasks - [ ] Name the configuration a computing unit cannot start without - [ ] Curate computing-unit images - [ ] Pre-pull curated images onto every node - [ ] Manage curated images from the admin page - [ ] Pick a curated image when creating a computing unit -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
