Skip to content

v0.30.3

Choose a tag to compare

View all tags
@DavidsonGomes DavidsonGomes released this 24 Apr 01:08
v0.30.3
271f9e5

EvoNexus v0.30.3 — Multi-arch Docker Images

Patch release completing the Docker Hub migration: images now ship as multi-arch manifests so ARM hosts can pull without platform overrides.

What's New

linux/amd64 + linux/arm64 in every tag

Every tag under evoapicloud/evo-nexus-{dashboard,runtime} now ships a manifest list covering both architectures:

  • amd64 — existing flow (x86_64 servers, traditional VPS)
  • arm64 — Apple Silicon (M1/M2/M3 Macs), AWS Graviton, Oracle Cloud ARM free tier, Raspberry Pi, most modern ARM VPS
# Works on any platform — Docker auto-picks the right arch
docker pull evoapicloud/evo-nexus-dashboard:v0.30.3

# Inspect the manifest to confirm multi-arch
docker buildx imagetools inspect evoapicloud/evo-nexus-dashboard:v0.30.3

Under the hood: the publish workflow runs docker/setup-qemu-action@v3 to emulate arm64 on the amd64 GitHub runners, then passes platforms: linux/amd64,linux/arm64 to build-push-action. The node-pty native addon compiles from source via node-gyp inside each builder, so there's no prebuilt-binary-per-arch concern.

Repo cleanup

  • Removed evonexus.portainer.stack.yml — it was a pre-configured stack pointing at a fork's namespace (marcelolealhub/*) and a specific host (advancedbot.com.br), which could mislead new users into pulling from the wrong registry. The canonical template at evonexus.stack.yml already supports Portainer/Traefik deployments and points at the official images.

Full Changelog: v0.30.2...v0.30.3

Assets 2
Loading