Custom Docker images in Snowpark Container Services: what the current docs say, and where "always linux/amd64" stopped being true
The question
"What do current Snowflake docs say about Snowpark Container Services custom Docker images — the exact area that stumped the founder on the GES-C02 exam — enough to turn into a short credibility post or community-forum answer?"
Context: the founder passed GES-C02 on 2026-09-28 and named "how to handle custom docker images in Snowpark Container Services" as the out-of-the-blue topic. This brief converts that gap into doc-verified material for a short post or a forum answer.
Verification key used below: [fetched] = read on a docs.snowflake.com page fetched 2026-11-13. [snippet] = seen only in a search-result summary of a docs.snowflake.com page, page not fetched. [unverified] = not confirmed against any current doc page.
What we already know (from the vault)
- The founder's first-hand report: the exam was multi-select "best two or three", did not drill syntax, and the SPCS custom-image topic was a surprise because the study plan had demoted SPCS to overview level after the C02 reweighting ([[founder-exam-experience-2026-09-28]]). The note records exam shape only, so we have no record of what the exam key expected.
- Our own study note covers the concept list (compute pool, image registry, service, job, service function, spec YAML) but is thin on the image workflow and has four statements that do not match the current docs (listed under Convergences) ([[study-snowpark-container-services]]).
- A colleague's pass checklist tested SPCS from the model-serving side: GPU compute pool families with the
GPU_prefix plus a service specification, and key-pair to JWT to OAuth for public endpoints ([[colleague-pass-checklist-kaulab-basu]]). - The 2026-09-28 log entry already floated a LinkedIn post ("studied for the wrong exam and passed anyway") that was awaiting the founder's yes ([[cert-progress]]). This brief is a different, narrower angle.
What the web says
- Registry and repository objects. Snowflake describes the registry as "an OCIv2-compliant image registry service". An image repository is a schema-level object, and creating one needs the CREATE IMAGE REPOSITORY privilege on the schema. Repository privileges are READ (list and pull), WRITE (also push) and OWNERSHIP, plus SERVICE READ / SERVICE WRITE used by the model-serving image build. Access control is per repository; image-level access control is not supported [fetched: registry and repository page].
- URL format. Registry hostname is
<orgname>-<acctname>.registry.snowflakecomputing.com, always lowercase, with underscores in the account name replaced by dashes. Repository URL is<registry-hostname>/<db_name>/<schema_name>/<repository_name>, andSHOW IMAGE REPOSITORIESreturns it. Double-quoted names with special characters are not supported. One example on the page usesregistry.snowflake.cominstead ofregistry.snowflakecomputing.com, which reads as a doc typo [fetched: same page]. - Auth. The documented path is
snow spcs image-registry login(Snowflake CLI, which supports all Snowflake auth forms).snow spcs image-registry tokenissues a token for any OCI client. A programmatic access token also works withdocker login. Plain username/password is off by default because it cannot satisfy multi-factor authentication throughdocker login; an account administrator has to enable it [fetched: same page]. Key-pair specifics for the registry were not on the page [unverified]. - Build and push. Tutorial 1 builds with
docker build --rm --platform linux/amd64 -t <repository_url>/<image_name> ., logs in withsnow spcs image-registry login, then runsdocker push <repository_url>/<image_name>. It has no separatedocker tagstep because the build tags with the full URL [fetched: Tutorial 1]. Listing isSHOW IMAGES IN IMAGE REPOSITORY[fetched: registry page]; the CLI equivalentsnow spcs image-repository list-imagesexists per the CLI docs [snippet]. - Spec reference. In the service spec,
nameandimageare the only required container fields. Theimagevalue is the repository path without the registry hostname, for example/tutorial_db/data_schema/tutorial_repository/my_echo_service_image:latest.commandoverrides the Dockerfile ENTRYPOINT andargsoverrides CMD. A GPU request needs a matching limit undernvidia.com/gpuor the container gets no GPU. The service is created withCREATE SERVICE ... IN COMPUTE POOL ... FROM SPECIFICATION[fetched: specification reference, Tutorial 1]. - Platform is no longer amd64-only. The spec reference now says images "must match the CPU architecture of the compute pool's instance family":
linux/amd64for x86 families andlinux/arm64for ARM families [fetched]. An ARM family (GEN_ARM_G1) went generally available on AWS on 2026-05-15, and the instance-family page recommends multi-platform images for mixed deployments [snippet: release note]. Google Cloud availability in October 2026 came from a secondary aggregator [unverified]. Tutorial 1 still says "the linux/amd64 platform that Snowpark Container Services supports" [fetched], so the docs disagree with themselves. - Limits and lifecycle. Maximum compressed layer size is 160 GiB on AWS and 195 GiB on Azure, with no Google Cloud figure given. "Dropping images from a repository is currently not supported";
DROP IMAGE REPOSITORYremoves all of them. Inbound private connectivity to the registry is a contact-your-account-rep item [fetched: registry page]. - Not found in the fetched pages: image vulnerability scanning, a supported-base-image list, pulling service images from an external registry, registry storage pricing, and repository replication or encryption options. Treat all five as [unverified], not as "does not exist".
Convergences and contradictions
- Vault study note vs current docs. [[study-snowpark-container-services]] is wrong or stale in four places: it says to
PUTthe image (the docs usedocker push), listsUSAGEon the image repository (the docs list READ / WRITE / OWNERSHIP), shows a stage volume assource: "@my_stage"with atargetkey (the"@<stagename>"form is deprecated in favor ofsource: stagewithstageConfig, and the mount path lives under the container'svolumeMounts.mountPath), and namessnowsqlas an auth route (not on the current registry page). This brief does not edit that note. - Older material vs current product. Tutorials, and probably most prep material written before May 2026, teach "SPCS requires linux/amd64" as an absolute. Current reference docs make it conditional on the compute pool's instance family. We have no evidence of what the GES-C02 key expects, so the safe exam answer and the correct production answer may differ. That gap is the interesting part of a post.
- Agreement. The colleague checklist's framing (GPU pool + service specification for custom model serving) matches the docs' shape: image in a repository, spec referencing it, service created in a compute pool.
Synthesis for RDCO
The founder's gap was a workflow gap, not a concept gap. Our notes knew what a registry and a spec were, but not the five-step chain that a "best two or three" question tests: create a repository in a schema, get its URL from SHOW IMAGE REPOSITORIES, build for the pool's architecture and tag with the full URL, authenticate Docker through Snowflake, push, then reference the image in the spec by path without the hostname. Each step has one detail that makes a good distractor: lowercase hostname with dashes, MFA blocking password docker login, WRITE rather than READ to push, hostname-less image path in the spec, no per-image delete.
The credibility angle is the amd64 change. Almost every tutorial and study guide says "build with --platform linux/amd64" as a rule, and Snowflake's own Tutorial 1 still does. The spec reference now says to match the compute pool's instance family, with linux/arm64 for ARM pools. A post that says "I got surprised by this topic on the exam, went back to the docs, and the rule everyone repeats is now conditional" is specific, checkable and useful to someone debugging a failed service on an ARM pool. It also fits the positioning of agents and data work in production rather than cert trivia. Before publishing, the ARM release note and instance-family page should be read directly, since this brief saw them only as search snippets.
Two guardrails. The post must stay on public docs and exam shape; the vault note is explicit that reproducing exam questions breaches the Snowflake exam agreement, so "the exam asked X" is out and "this topic showed up and I was underprepared" is in. And the unverified items (scanning, external registries, key-pair for the registry) should not appear as claims in either the post or a forum answer.
Draft outline, short post or forum answer (not the full piece; the "I" lines are placeholders for the founder's own words):
- Hook (1-2 lines): passed GES-C02, and the topic that caught me out was custom Docker images in SPCS. Went back to the current docs. Here is the whole workflow in six lines, plus one rule that changed.
- The chain:
CREATE IMAGE REPOSITORYin a schema ->SHOW IMAGE REPOSITORIESfor the URL ->docker build --platform <arch> -t <repository_url>/<image>:<tag> .->snow spcs image-registry login->docker push-> reference it in the spec as/db/schema/repo/image:tag. - Four details that bite: hostname is lowercase and underscores become dashes; password
docker loginfails under MFA, so use the CLI login or a programmatic access token; pushing needs WRITE on the repository; the spec's image path has no registry hostname. - The rule that changed: "always linux/amd64" is now "match the compute pool's instance family" -
linux/arm64on ARM pools. Note that Tutorial 1 still says amd64-only, and link both pages. - Housekeeping: you cannot drop a single image, only the repository; layer size caps differ by cloud.
- Close: one line on why it matters outside the exam (custom model serving on GPU pools), plus links to the three doc pages.
Forum-answer variant: lead with item 2 or item 4 depending on the question asked, keep item 3 as a checklist, drop the exam framing.
Why this is in the vault
It feeds the community-watch and credibility-content lane with a doc-verified answer pack on SPCS custom images, sourced from the founder's own GES-C02 gap recorded in [[founder-exam-experience-2026-09-28]]. It also flags four stale statements in [[study-snowpark-container-services]] for whoever next uses that note for cert prep.
Open follow-ups
- Do the 2026-05-15 ARM release note and the instance-families pages confirm exactly which clouds and regions have ARM compute pools today, and does a multi-platform manifest pushed to an SPCS repository resolve correctly on both x86 and ARM pools?
- Does Snowflake document any image vulnerability scanning for SPCS repositories, or any way for a service spec to reference an image outside the account's own repository (external registry, or a shared image via Native Apps)?
- What does the current
CREATE IMAGE REPOSITORYreference page list as parameters and limits (encryption, replication, per-account repository or storage quotas, storage billing)?
Related
- [[founder-exam-experience-2026-09-28]]
- [[study-snowpark-container-services]]
- [[colleague-pass-checklist-kaulab-basu]]
- [[cert-progress]]
- [[2026-06-18-snowpro-genai-specialty-c02-exam-structure]]
- [[2026-11-10-snowflake-eai-privileges-and-coding-agent-sandbox-egress]]
Sources
Vault:
- [[founder-exam-experience-2026-09-28]] (01-projects/certifications/snowpro-genai-c02/)
- [[study-snowpark-container-services]] (01-projects/certifications/snowpro-genai-c02/)
- [[colleague-pass-checklist-kaulab-basu]] (01-projects/certifications/snowpro-genai-c02/)
- [[cert-progress]] (01-projects/phdata/)
- [[2026-06-18-snowpro-genai-specialty-c02-exam-structure]] and [[2026-11-10-snowflake-eai-privileges-and-coding-agent-sandbox-egress]] are adjacent briefs listed for graph traversal; they were not read for this brief.
Web, fetched 2026-11-13:
- https://docs.snowflake.com/en/developer-guide/snowpark-container-services/working-with-registry-repository
- https://docs.snowflake.com/en/developer-guide/snowpark-container-services/specification-reference
- https://docs.snowflake.com/en/developer-guide/snowpark-container-services/tutorials/tutorial-1
Web, search snippet only (not fetched):
- https://docs.snowflake.com/en/release-notes/2026/other/2026-05-15-spcs-gen-arm-g1-ga
- https://docs.snowflake.com/developer-guide/snowpark-container-services/instance-families-aws
- https://docs.snowflake.com/en/developer-guide/snowflake-cli/services/manage-images
- https://docs.snowflake.com/en/developer-guide/snowpark-container-services/spcs-guidelines-and-limitations
Research caps used: QMD 1 query, WebSearch 3, WebFetch 3 sources (the specification reference was queried twice for verbatim quotes).