OpenClaw Azure Container Apps Deploy
suresh-deccansoft/openclaw-aca-plugin
Deploy automático do OpenClaw no ACA com troubleshooting integrado
Ver no GitHubPlugin Claude Code que automatiza o deployment do OpenClaw no Azure Container Apps com um assistente guiado. Encapsula quatro armadilhas conhecidas (BuildKit, Azure Files SMB, IPv6, gateway mode) e oferece duas estratégias de persistência de estado: sincronização local periódica (barata) ou NFS premium em VNet (resiliente).
Instalação
npx convez-ai suresh-deccansoft/openclaw-aca-plugin1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.
Métricas
Casos de uso
- Implantar bots OpenClaw/Telegram no Azure sem cair em armadilhas de BuildKit e SMB
- Escolher e configurar estratégia de persistência de conversas (local+sync vs NFS premium)
- Diagnosticar deployments silenciosos ou quebrados com o agente openclaw-azure-doctor
Veredito

Plugin especializado e bem documentado que resolve problemas reais de deployment do OpenClaw no Azure com automação robusta. Recomendado para quem já trabalha com Azure Container Apps e bots Telegram; requer familiaridade prévia com ACA e Docker.
README
A tradução para o português deste README ainda está na fila.
Deccansoft Claude Code plugins
A Claude Code plugin marketplace. Currently ships one plugin:
openclaw-azure — deploy OpenClaw to Azure Container Apps
A guided deploy wizard that gets OpenClaw running on Azure Container Apps correctly the first time — packaging a set of non-obvious pitfalls we hit the hard way so you don't have to.
Why this exists
Deploying OpenClaw to ACA looks simple but has four traps that each cost real time:
- The image needs BuildKit. OpenClaw's
DockerfileusesRUN --mount=..., which the classic builder behindaz acr buildrejects. You must build with BuildKit (we do it in-cloud via an ACR task, which also gives a fast network for the heavypnpm install). - Azure Files SMB silently breaks the bot. OpenClaw's Telegram ingress spool claims each update
with a hard link (
link()). SMB file shares don't support hard links and returnENOTSUP— so messages are received but never processed, and the bot goes silent with no obvious error. Mounting an SMB share at the state dir is the natural thing to do, and it's wrong. - Container Apps IPv6 egress to
api.telegram.orgstalls, adding ~10–15s to every Telegram call until a fallback kicks in. You must force IPv4. gateway.mode: localis mandatory or the gateway refuses to start.
This plugin encodes all of that into a /openclaw-azure:deploy wizard, a troubleshooting agent, and
reference docs.
Persistence: you choose
The wizard asks how you want conversation memory to survive updates/restarts:
| Model | Memory survives restart | Crash loss | Extra cost | What the wizard does |
|---|---|---|---|---|
| Local + periodic sync (default) | ✅ (final sync on SIGTERM) | ≤ last sync interval on a hard crash | ~$0–1/mo (Standard SMB) | Keeps state on local disk (hard links work) and backs it up to a cheap SMB share every 5 min + on shutdown |
| Premium NFS + VNet | ✅ real-time | none | ~$15/mo + VNet | Provisions premium Azure Files NFS (NFS 4.1 supports hard links) and a VNet-integrated environment, mounted directly at the state dir |
See plugins/openclaw-azure/skills/deploy-openclaw/references/azure-files-limitations.md
for the full explanation of why SMB can't back the state dir.
Install
/plugin marketplace add suresh-deccansoft/openclaw-aca-plugin
/plugin install openclaw-azure@deccansoft-claude-plugins
Then run:
/openclaw-azure:deploy
What's in the plugin
/openclaw-azure:deploy— phased deploy wizard (preflight → inputs → BuildKit build → persistence choice → deploy → verify).openclaw-azure-doctoragent — diagnoses a silent or broken deployment from the logs.- Reference docs — Azure Files limitations, persistence comparison, and the full gotchas list.
- Bundled scripts — preflight, BuildKit build, both deploy paths, and log verification.
Support
Questions, issues, or feature requests: aiteam@deccansoft.net, or open an issue at https://github.com/suresh-deccansoft/openclaw-aca-plugin/issues.
Privacy: see PRIVACY.md — the plugin collects no data and sends nothing to its authors.
License
MIT.