# \[Bug\]: Antigravity runtime install fails on Debian VMs that use GCE OS Login · Issue \#23005 · pingdotgg/t3code

[View on GitCafe](https://git.cafe/pingdotgg/t3code/issues/23005)

Repository: [pingdotgg/t3code](https://git.cafe/pingdotgg/t3code)

Visibility: public

State: backlog

Priority: 0

## Description

[Discussion and activity](https://git.cafe/pingdotgg/t3code/issues/23005)

---

### Before submitting

- [x] I searched existing issues and did not find a duplicate.
- [x] I included enough detail to reproduce or investigate the problem.

### Area

apps/server

### Steps to reproduce

1. Run T3 on a Debian 13 GCE VM with OS Login enabled, as an OS Login user. These users are not in `/etc/passwd`, and `/etc/nsswitch.conf` has `passwd: files cache_oslogin oslogin`.
2. Settings > Providers > Antigravity > Install.

Standalone repro with the managed 1.3.0 runtime (`agy-acp-server-1.3.0-linux-x86_64.zip`), started the way T3 starts it:

```sh
printf '%s\n' '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":1,"clientCapabilities":{}}}' \
  | ./agy_acp_server.par --uid=
echo $?   # 255, nothing on stdout or stderr
```

### Expected behavior

The runtime installs and answers ACP `initialize`.

### Actual behavior

Install fails with "The downloaded Antigravity runtime could not start in this environment." (ACP process exited with code 255), and T3 deletes the download.

The process exits before speaking ACP, with no output. The `.par` loads its own libgcc_s from a memfd. To resolve the current user it calls `getpwuid_r`, which loads `libnss_oslogin.so.2` (from `google-compute-engine-oslogin` 20260924.00). That module links the system libstdc++, which can't bind against the bundled libgcc_s, so the lookup fails and the server exits. `LD_DEBUG=libs` shows:

```
trying file=/lib/x86_64-linux-gnu/libnss_oslogin.so.2
/proc/self/fd/5: error: version lookup error: version `GCC_4.3.0' not found (required by /lib/x86_64-linux-gnu/libstdc++.so.6) (fatal)
```

Users listed in `/etc/passwd` are presumably unaffected, since `files` answers before the OS Login module loads. Runtime 1.4.1, the current ACP registry version, behaves the same.

### Impact

Blocks work completely

### Version or commit

T3 0.1.2-nightly.20261021.3473; Antigravity ACP runtime 1.3.0

### Environment

Debian 13 (trixie) GCE VM, kernel 6.12.111+deb13-cloud-amd64, OS Login enabled, google-compute-engine-oslogin 1:20260924.00-g1+deb13

### Logs or stack traces

```shell

```

### Screenshots, recordings, or supporting files

_No response_

### Workaround

Preload the system libgcc_s. With `LD_PRELOAD=/lib/x86_64-linux-gnu/libgcc_s.so.1` the same command returns a normal `initialize` result. I put that in a wrapper script and pointed the Antigravity binary path at it, with a `localharness_external` symlink next to it. Adding the user to `/etc/passwd` should also work, but needs root.