fix(install): warn loudly on non-x86_64 architectures before pulling images#797
Merged
jakeaturner merged 1 commit intodevfrom Apr 28, 2026
Merged
fix(install): warn loudly on non-x86_64 architectures before pulling images#797jakeaturner merged 1 commit intodevfrom
jakeaturner merged 1 commit intodevfrom
Conversation
…images Detects the host architecture early in the preflight sequence. On any architecture other than x86_64/amd64, prints a 5-line warning that NOMAD officially supports x86_64 only, points at PR #419, and sleeps 10 seconds before continuing. Ctrl+C aborts cleanly before any Docker work happens. Preserves the community/hacker path: ARM64 users running with QEMU binfmt_misc emulation can still let the install proceed. The change just stops the silent 2.7GB amd64 pull on architectures where it will not work, which leaves partial images and /opt/project-nomad/ debris that confuse first-time users. Reported in #782.
chriscrosstalk
added
enhancement
4 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Reported in #782 by @Dinsmoor on a DGX Spark (ARM64). The install script currently has no architecture precheck, so on ARM64/aarch64 hosts it pulls ~2.7GB of amd64 Docker images that won't run, then fails partway through with a vague "Cannot connect to the Docker daemon" error. The user is left to manually clean up partial images and
/opt/project-nomad/.Approach
Adds
check_is_x86_64()to the preflight sequence (modeled on the existingcheck_is_debian_based()pattern at line 79). On any architecture other than x86_64/amd64:Why warn-and-continue instead of hard exit
A hard exit would block the community/hacker path: ARM64 users with QEMU binfmt_misc emulation set up can run amd64 images (slowly), and #487 explicitly framed ARM64 as community-supported for now. The warn-and-countdown approach addresses the real user-facing complaint (silent waste of bandwidth + leftover debris) without locking out adventurous users.
Test plan
bash -n install/install_nomad.sh(syntax check passes)Architecture check passed (x86_64)is printed, install proceedsNotes
This does not address the broader cleanup-on-failure ask from #782 (trapping partial-install state and rolling it back). That's a larger scope and worth its own PR.