solution docker medium linux macos windows

Docker: 'This version of Antigravity is no longer supported' (update required)

When Antigravity rejects requests with an update-required message, upgrade OpenClaw (or rebuild your Docker image) and re-authenticate.

By CoClaw Team •

Symptoms

  • Gateway logs or the Control UI show an error like:
    • “This version of Antigravity is no longer supported. Please update to receive the latest features!”
  • Requests routed through google-antigravity/... stop working (suddenly or after a long time).

Cause

Antigravity is a hosted bridge and it can enforce minimum client versions. If your OpenClaw Docker image is older (or your gateway has cached older plugin/client code), Antigravity may refuse requests.

Fix

1) Update OpenClaw in your Docker deployment

If you run from an OpenClaw repo checkout:

  1. Pull the latest OpenClaw changes.
  2. Rebuild the Docker image.
  3. Restart the gateway container.

If you used docker-setup.sh, the simplest path is to rerun it from a fresh checkout (it rebuilds and restarts).

2) Re-authenticate if needed

Some updates require re-auth (or your token expired). After updating, rerun your provider auth flow (for example, via openclaw onboard on the gateway host/container).

3) Temporary workaround: switch providers/models

If you need to stay online while debugging:

  • Switch the primary model away from google-antigravity/... to another configured provider, or
  • Add a fallback model from a different provider.

Verify

  • A test message succeeds and gateway logs no longer show the Antigravity update warning.
  • openclaw models status --probe succeeds for your configured model(s).

Verification & references

  • Reviewed by:CoClaw Editorial Team
  • Last reviewed:March 14, 2026
  • Verified on: Linux · macOS · Windows

References

Official docs

  1. OpenClaw docs: /concepts/model-providers
  2. OpenClaw docs: /install/updating

Issue threads

  1. OpenClaw GitHub issue #4111
Want to explore more? Browse all solutions or ask in the Community Forum .
Report a problem

Related Resources

Docker: docker-setup.sh or image build fails
Fix
Fix common Docker onboarding/build failures by rebuilding with correct deps, adding apt packages, checking Docker Desktop file sharing, and reading compose logs.
Docker: EACCES permission denied writing ~/.openclaw (openclaw.json.*.tmp)
Fix
Fix Docker permission errors when the gateway container can't write to the bind-mounted ~/.openclaw directory (common when host UID/GID != 1000).
Gateway: 'disconnected (1008): pairing required' after update (scope-upgrade / operator.write)
Fix
If new connections (Control UI, sub-agents, cron announce, webchat) are rejected with WebSocket 1008 'pairing required' after an update or reinstall, you may need to approve a device scope-upgrade (often `operator.write`).
Windows: tools.exec cannot find docker, rg, or gh even though they work in PowerShell
Fix
Fix native Windows cases where the Scheduled Task gateway uses a different PATH than your interactive shell, so tools.exec cannot resolve installed CLI tools.
Self-Hosting OpenClaw with Docker
Guide
Run a containerized OpenClaw Gateway with Docker Compose for an isolated, reproducible setup.
OpenClaw Installation Troubleshooting: Node/NPM, PATH, Windows (WSL2), and Docker
Guide
A layered checklist for the most common 'can't install' / 'command not found' / 'service won't start' failures. Covers Node version, global install permissions, PATH issues, WSL2 systemd, and Docker setup gotchas.