Install Nextstrain CLI from a standalone archive instead of PyPI #273
Conversation
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
This avoids issues of mutual incompatibility between Nextstrain CLI dependencies and other things we install into the container's default Python. Those aren't hypothetical; we've run into them before and worked around in other ways, e.g. "Isolate AWS CLI (v1) into its own Python venv" (d041d6c). This also aligns with our recommended and most common installation method.
Member
Author
|
I've had this code waiting in the wings for a bit. It needs an aarch64-unknown-linux-pc build of Nextstrain CLI, which I also have a WIP for. I'll either get that going quickly or push it up and PR it as-is and cross-link the PRs. |
tsibley
added a commit
to nextstrain/cli
that referenced
this pull request
Nov 6, 2025
GitHub released public runners.¹ This will ultimately let us use standalone installation archives in our linux/arm64 Docker images.² Changes to the standalone installer to follow separately³, as those need to be held for merge until after the first release with these builds available. ¹ <https://github.blog/changelog/2025-01-16-linux-arm64-hosted-runners-now-available-for-free-in-public-repositories-public-preview/> ² <nextstrain/docker-base#273> ³ <https://github.com/nextstrain/cli/pull/490>
2 tasks
tsibley
added a commit
to nextstrain/cli
that referenced
this pull request
Nov 6, 2025
GitHub released public runners.¹ This will ultimately let us use standalone installation archives in our linux/arm64 Docker images.² Changes to the standalone installer to follow separately³, as those need to be held for merge until after the first release with these builds available. ¹ <https://github.blog/changelog/2025-01-16-linux-arm64-hosted-runners-now-available-for-free-in-public-repositories-public-preview/> ² <nextstrain/docker-base#273> ³ <#490>
Member
|
The aarch64 build isn't strictly necessary – the x86_64 build can be run using emulation like many other tools in the image – but producing the platform-native build for Nextstrain CLI seems simple enough that we can wait for that here. |
Member
Author
|
Yeah, good point! I'd forgotten that we still require x86_64 emulation for the aarch64 image, since Nextstrain CLI no longer requires emulation for itself. Aside from several testing infra hurdles for aarch64, the builds work just fine, so I'll get them going. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This avoids issues of mutual incompatibility between Nextstrain CLI dependencies and other things we install into the container's default Python. Those aren't hypothetical; we've run into them before and worked around in other ways, e.g. "Isolate AWS CLI (v1) into its own Python venv" (d041d6c).
This also aligns with our recommended and most common installation method.
Checklist