ProxmoxMCP-Plus v0.5.11

Release date: 2026-07-29

Native ARM64 Container Image

This release publishes the GHCR container for both linux/amd64 and linux/arm64 under the same image tags.

Docker now selects the native image automatically on Apple Silicon and other ARM64 hosts. These systems no longer need to run the AMD64 image through QEMU emulation when pulling the published image.

Release Pipeline Safety

The release workflow uses Docker Buildx to publish one multi-architecture manifest. QEMU registration is limited to ARM64, the only additional target. The newly introduced QEMU and Buildx actions are pinned to reviewed full commit SHAs, and the QEMU helper image is pinned by OCI digest.

The Docker build context now excludes local agent/tool state, environment files, private-key file patterns, and non-example Proxmox JSON configuration files. This prevents local development credentials or runtime configuration from being copied into image layers by COPY . ..

Python packaging tools (pip, setuptools, and wheel) are removed after the application is installed because they are not required at runtime. This reduces the final image attack surface and prevents vulnerabilities in dormant build-only code from shipping with the service.

The multi-architecture Python base image is pinned by OCI digest. Regression tests verify that both architectures remain configured, the new third-party actions remain immutable, the sensitive build-context exclusions remain present, the base image remains immutable, and the runtime packaging toolchain remains removed.

After publication, a native GitHub-hosted ARM64 runner pulls the published image, verifies that the tag contains both Linux architectures, starts the ARM64 container, checks /livez, confirms uname -m reports aarch64, and confirms the process is not running as root. The GHCR workflow does not pass unless this post-publication check succeeds.

Container Vulnerability Review

Docker Scout analysis removed two high-severity findings by removing the dormant Python packaging toolchain. The remaining findings are in Debian Trixie's essential perl-base package:

• CVE-2026-12087
• CVE-2026-48959
• CVE-2026-48962

Debian classifies these as minor no-dsa issues for Trixie, and the current Trixie repository does not provide a fixed package. Their vulnerable paths require an application to invoke Perl Socket or Perl archive-processing APIs with attacker-controlled inputs. ProxmoxMCP-Plus does not invoke Perl or expose those APIs. Removing the essential package would make the base system unsafe, so the residual base-image advisories are documented rather than hidden or bypassed.

Compatibility

• Existing AMD64 deployments continue to receive a native AMD64 image.
• ARM64 hosts receive a native ARM64 image from the same tag.
• Image names, ports, environment variables, transports, and MCP tools are unchanged.
• No runtime configuration migration is required.

Validation

The release quality gate covers Python 3.11 and 3.12 tests with coverage enforcement, Ruff, Mypy, CodeQL, dependency auditing, package builds, Twine metadata validation, runtime-to-manifest parity, multi-architecture workflow regression checks, and Docker build-context safety checks.

The published 0.5.11 and latest tags must expose both linux/amd64 and linux/arm64. The ARM64 image is pulled explicitly on a native ARM64 runner and its application health endpoint is checked before issue #109 is closed.

Upgrade Notes

• Pull ghcr.io/rekklesna/proxmoxmcp-plus:0.5.11 or latest normally.
• Docker automatically selects the correct architecture.
• No Compose or MCP client changes are required.