[BUG] Antigravity CLI install fails on musl hosts + SegFault on cpu, that not support AES-ni

On musl hosts (alpine linux, chimera linux) install.sh cant find an musl manifest on server (cdn returns 404)

In my case, binary in docker container, runned on i3 540 returns SegFault (go bin compiled w\ hardware AES-ni, but i3 540 dont have it)

What u can do:

  1. Re-upload musl manigest to cdn
  2. Re-compile binary with GOARCH=amd64 GOAMD64=v1 and mark as "for legacy devices

i3-540:~# ping google.com
PING (142.251.14.101): 56 data bytes # link is deleted bcause forun allow only 2 links
64 bytes from 142.251.14.101: seq=0 ttl=112 time=86.803 ms
64 bytes from 142.251.14.101: seq=1 ttl=112 time=86.247 ms
^C
— ping statistics —
2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max = 86.247/86.525/86.803 ms
i3-540:~# curl -fsSL https://antigravity.google/cli/install.sh | bash
⠋ Detecting system environment…
âś“ Platform detected: linux_amd64_musl
⠋ Querying release repository…
Fatal: Could not connect to the release server to download the manifest. Please check your internet connection or firewall settings.
i3-540:~#

1 Like