Air-Gapped Deployment
Alpamayo1.5 NIM can run without outbound network access after its container image and one model profile have been staged on an internet-connected system. Use the same NIM image digest and GPU class on the connected and disconnected systems.
Prepare the Offline Cache
On an internet-connected system with a supported GPU, authenticate to NGC and create a local-disk cache that the container user (UID 1000) can write:
List the profiles compatible with the connected system. The command writes machine-readable output into the mounted cache:
Select a compatible profile by its profile_name tag. The following command selects the precision in PROFILE_NAME and fails if it is not compatible:
Download that exact profile without starting the inference server:
Package the image, cache, and selected profile ID for transfer through your approved media or artifact process:
Start on the Air-Gapped System
Transfer the four generated files to the disconnected system. Load the image and restore the writable cache:
Create an internal Docker network, which permits host-to-container port publishing but has no external route, and start the NIM on that network:
NGC_API_KEY is not required when the complete profile is cached. If your deployment platform injects the key, it can remain present; the internal Docker network is the isolation control that prevents outbound access.
The cache must remain writable because startup can create profile-specific patched model metadata and local runtime artifacts. A read-only cache is not supported.
Verify the Deployment
From the disconnected host, verify readiness and model metadata:
If startup attempts an NGC download, confirm that NIM_MODEL_PROFILE exactly matches the staged profile ID, the complete cache was transferred, and the cache is mounted at /opt/nim/.cache.