Build arm64 image, drop Azure ACI deploy#71
Open
TaprootFreak wants to merge 1 commit into
Open
Conversation
The CI built a single linux/amd64 image and shipped it to Azure Container Instances. Per project convention DFX containers are arm64- only now, and Azure is being retired (see "ARM64-only Builds" and "Kein Azure mehr"). The arm64-only build also closes the manifest- mismatch that broke the dfxdev/dfxprd hummingbot stack: those servers pull arm64 and the previous workflow only pushed amd64. - Build matrix: linux/arm64 only, on ubuntu-24.04-arm. - Image tags: :beta / :latest (per env stage) plus :sha for reproducibility. - Removed all Azure-specific steps (az login, container stop/delete, container create) and the rendered ACI YAMLs they consumed (aci-dev.yaml, aci-prd.yaml, aci-keep-market-*.yaml). - Image-published dispatch to the server repo, identical to the nanobot pattern: server-repo CI picks it up and rolls the stack on dfxdev / dfxprd. Azure ACI instances must be retired separately (manual `az container delete` for ci-dfx-hb-*-dev / ci-dfx-hb-*-prd).
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
1 participant
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.
Summary
no matching manifest for linux/arm64/v8.linux/arm64onubuntu-24.04-arm. Tags::beta(DEV) /:latest(PRD) plus:<sha>for reproducibility.aci-*.yaml).Requires before merge
DISPATCH_TOKEN(PAT withreposcope, can dispatch toDFXServer/server) andDISPATCH_REPO=DFXServer/serverset in this repo's Actions secrets. Without them the workflow still builds + pushes, only the deploy notification is skipped (warning logged).Manual follow-up after merge
The existing Azure container instances will keep running after this change. Decide whether to retire them:
az container delete --resource-group rg-dfx-api-dev --name ci-dfx-hb-{deuro-usdt,deps-usdt,jusd-usdt,keep-market}-dev --yes az container delete --resource-group rg-dfx-api-prd --name ci-dfx-hb-{deuro-usdt,deps-usdt,keep-market}-prd --yesPlus the Azure-only secrets (
DFX_DEV_CREDENTIALS,DFX_PRD_CREDENTIALS) can be removed from the repo once the migration is confirmed.Test plan
dfxswiss/hummingbot:beta+:<sha>on push todevelop.DISPATCH_TOKEN: workflow finishes green with a warning, no dispatch.DISPATCH_TOKEN: server-repo CI receives the dispatch and deploys thehummingbotstack on dfxdev.docker manifest inspect dfxswiss/hummingbot:betashowslinux/arm64entry.