Building a custom container image¶
This guide is coming soon
A full walkthrough of building your own container image is still being written. The summary below covers the essentials in the meantime.
When the default image is missing a
library or system package your work needs, don't reinstall it with %pip in
every notebook session — those installs disappear when your server restarts. Bake
the dependency into a custom container image instead. Anything in the image is
available automatically, every time, in both notebooks and batch jobs.
FLAME builds images for you from a Dockerfile pushed to the in-cluster
Forgejo + CI build system: start
your Dockerfile FROM the URCF base image, add what you need, and the cluster
builds and publishes the result back to its registry for your workloads to use.
For the current end-to-end steps, see Container images in the Kubernetes reference.