By devasher · Edited by Nominiclaw
This update introduces runtime-agnostic container build arguments, enhanced ACPX startup tracing for better performance attribution, and critical dependency updates.
OpenClaw v2026.5.19-beta.2 focuses on improving the developer experience for containerized deployments and providing deeper observability into the Gateway's startup sequence. By refining how system packages are handled during image builds and instrumenting the ACPX startup probe, this release provides maintainers and users with better tools for optimization and deployment flexibility.
To better support a variety of container runtimes, OpenClaw has introduced a more generic approach to handling additional system packages during image builds.
OPENCLAW_IMAGE_APT_PACKAGES is now the preferred environment variable for specifying extra apt packages. This replaces the Docker-specific naming convention to ensure the build process is runtime-neutral, benefiting users of both Docker and Podman.OPENCLAW_DOCKER_APT_PACKAGES variable remains supported as a fallback. If both are provided, OPENCLAW_IMAGE_APT_PACKAGES takes precedence.This release introduces detailed instrumentation for the ACPX startup probe within Gateway restart traces. Previously, the time spent on the ACPX startup probe was aggregated under a broad "plugin-service" cost, making it difficult to pinpoint the exact cause of startup delays.
@openclaw/proxyline updated to 0.3.3.0.75.1.For most users, this is a transparent update. However, developers and platform engineers will see the following impacts:
OPENCLAW_IMAGE_APT_PACKAGES variable more intuitive and consistent with the project's runtime-agnostic goals.sidecars.plugin-services.acpx.acpx-runtime.probe.availability) to identify exactly where time is being spent during the ACPX initialization phase.