Bug Report: Dev Container attach fails — remote-server tarball returns 404 from CDN

Google Antigravity
,
1

Summary

Attaching Antigravity IDE 2.0.1 to a Docker Dev Container fails during the remote-server install step. The installer script tries to download the Linux x64 reh tarball from Google’s CDN, but every candidate URL returns HTTP 404 Not Found. The Linux remote-server build for this IDE commit appears not to be published.

Environment

  • Antigravity IDE: 2.0.1 (commit bf9a033f33934fb4496d7eebed52486272437c3a, quality stable)

  • VS Code base: 1.107.0

  • Host OS: Windows 10.0.26200 x64

  • Docker Desktop: 4.63.0 (220185), Engine 29.2.1

  • Container OS: AlmaLinux 10.1 (Heliotrope Lion), x86_64, glibc 2.28+

  • Container shell tools: GNU Wget 1.24.5, curl 8.12.1 (OpenSSL/3.5.1)

Steps to reproduce

  1. Have a running Docker container (fmkorea_sandbox, AlmaLinux 10.1 / x86_64).

  2. From Antigravity IDE on Windows, run “Dev Containers: Attach to Running Container…” against that container.

  3. The IDE invokes the server install script inside the container.

Expected

The Linux x64 remote-server tarball is downloaded, extracted under ~/.antigravity-ide-server/bin/<version>-<commit>/, and the extension host starts listening.

Actual

The install script tries 4 URLs in order, and every one returns HTTP 404:

https://edgedl.me.gvt1.com/edgedl/release2/j0qc3/antigravity/stable/2.0.1-bf9a033f33934fb4496d7eebed52486272437c3a/linux-x64/Antigravity-reh.tar.gz
https://redirector.gvt1.com/edgedl/release2/j0qc3/antigravity/stable/2.0.1-bf9a033f33934fb4496d7eebed52486272437c3a/linux-x64/Antigravity-reh.tar.gz
https://edgedl.me.gvt1.com/edgedl/antigravity/stable/2.0.1-bf9a033f33934fb4496d7eebed52486272437c3a/linux-x64/Antigravity-reh.tar.gz
https://redirector.gvt1.com/edgedl/antigravity/stable/2.0.1-bf9a033f33934fb4496d7eebed52486272437c3a/linux-x64/Antigravity-reh.tar.gz

IDE output:

Download failed from <each URL above>, trying next URL...
Error downloading server from all URLs

Error: installation failed.
exitCode==1==
osReleaseId==almalinux==
arch==x86_64==
platform==linux==

Diagnosis (from inside the container)

Network, DNS, and HTTP clients are all healthy — the CDN itself is returning 404, so this is a publishing/availability issue, not a client-side network problem.

DNS resolves cleanly:

edgedl.me.gvt1.com   -> 34.104.35.123
redirector.gvt1.com  -> 142.250.23.100..139

curl -I against the first URL:

HTTP/2 404
content-length: 1449
content-type: text/html; charset=utf-8
server: Google-Edge-Cache
x-content-type-options: nosniff

wget (matches what the install script does, just with --tries=1):

--2026-05-20 00:23:41--  https://edgedl.me.gvt1.com/edgedl/antigravity/stable/2.0.1-bf9a033f.../linux-x64/Antigravity-reh.tar.gz
Resolving edgedl.me.gvt1.com (edgedl.me.gvt1.com)... 34.104.35.123
Connecting to edgedl.me.gvt1.com (edgedl.me.gvt1.com)|34.104.35.123|:443... connected.
HTTP request sent, awaiting response... 404 Not Found
2026-05-20 00:23:41 ERROR 404: Not Found.

So:

  • TCP/TLS to Google Edge Cache succeeds.

  • The server explicitly returns 404 (with server: Google-Edge-Cache headers), meaning the object is not present at any of the published paths.

  • The 2.0.1 / commit bf9a033f33934fb4496d7eebed52486272437c3a Linux x64 reh build looks like it was never uploaded (or was un-published) for the stable channel.

Impact

Any user on this IDE build cannot attach to a Linux x86_64 Dev Container (or, presumably, connect to any Linux remote host requiring this remote-server build) until the matching tarball is published.

2

Hi,

I’m unable to use Remote SSH in Antigravity IDE because the remote server installation fails.

From the logs, Antigravity attempts to download:

https://edgedl.me.gvt1.com/edgedl/release2/j0qc3/antigravity/stable/2.0.1-bf9a033f33934fb4496d7eebed52486272437c3a/linux-x64/Antigravity%20IDE-reh.tar.gz

and then falls back to:

https://redirector.gvt1.com/edgedl/release2/j0qc3/antigravity/stable/2.0.1-bf9a033f33934fb4496d7eebed52486272437c3a/linux-x64/Antigravity%20IDE-reh.tar.gz

I manually tested the download process. The redirector endpoint responds correctly with HTTP 302 and redirects to a CDN host, but the final CDN URL returns:

HTTP/1.1 404 Not Found

As a result, the server archive is never downloaded and Remote SSH cannot complete installation.

Additional observations:

  • DNS resolution works correctly.

  • HTTPS connectivity is working (Google and GitHub are reachable).

  • The issue reproduces both from the remote Linux machine and when following the redirect chain manually.

  • The build involved is: 2.0.1-bf9a033f33934fb4496d7eebed52486272437c3a

This appears to be a missing or unavailable server package on the CDN rather than a local SSH or networking issue.

Could you please investigate or provide a working server package for this build?

Thank you.