A county analytics function needs GraalVM packaging that the standard FDK runtime images do not cover. What advanced OCI Functions packaging path is documented?
Select an answer to reveal the explanation.
Short Explanation
Bring-your-own Dockerfile is the escape hatch when stock FDK images are not enough—including GraalVM cases. You still ship a function image, not an OKE Deployment.
Full Explanation
Official Functions docs allow a custom Dockerfile for cases the FDK runtimes do not cover, including GraalVM. That is an advanced packaging choice, not the default hello-world path, and the result remains a function image invoked by OCI Functions. It does not convert the workload into an OKE Deployment or replace the container model with raw source uploads.