# Can no longer connect to devcontainer after updating to v1.16.5

**URL:** <https://discuss.ai.google.dev/t/can-no-longer-connect-to-devcontainer-after-updating-to-v1-16-5/121479>\
**Category:** Google Antigravity\
**Tags:** bug\
**Created:** [February 5, 2026, 2:05pm UTC](https://discuss.ai.google.dev/t/can-no-longer-connect-to-devcontainer-after-updating-to-v1-16-5/121479 "2026-02-05T14:05:10Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![Alexander\_Roiatchki](https://d1dlmcr85iqnpo.cloudfront.net/user_avatar/discuss.ai.google.dev/alexander_roiatchki/32/90744_2.png) [@Alexander\_Roiatchki](https://discuss.ai.google.dev/u/Alexander_Roiatchki)\
**Post date:** [February 5, 2026, 2:05pm UTC](https://discuss.ai.google.dev/t/can-no-longer-connect-to-devcontainer-after-updating-to-v1-16-5/121479/1 "2026-02-05T14:05:10Z")

</div>

After updating to the new v.1.16.5 on Linux Antigravity can no longer connect to devcontainers and shows ‘Could not fetch remote environment. Failed to connect to the remote extension host server (Error: WebSocket close with status code 1006)’.

Here’s the tail of the output logs:

```auto
# Finish server setup

print_install_results_and_exit 0

[Info - 14:02:55.467] Install options: {

  "id": "90553e2afa56b5f21a3a7409",

  "vscodeVersion": "1.107.0",

  "ideVersion": "1.16.5",

  "commit": "1504c8cc4b34dbfbb4a97ebe954b3da2b5634516",

  "quality": "stable",

  "extensionIds": [],

  "envVariables": [],

  "useSocketPath": false,

  "serverApplicationName": "antigravity-server",

  "serverDataFolderName": ".antigravity-server",

  "distroId": "1504c8cc4b34dbfbb4a97ebe954b3da2b5634516"

}

[Info - 14:02:55.580] SSH Agent Forwarding: true

[Info - 14:02:55.647] Server install output:

Waiting for lock...

Lock acquired, proceeding with installation.

Server script already installed in /home/vscode/.antigravity-server/bin/1.16.5-1504c8cc4b34dbfbb4a97ebe954b3da2b5634516/bin/antigravity-server

Server script is already running /home/vscode/.antigravity-server/bin/1.16.5-1504c8cc4b34dbfbb4a97ebe954b3da2b5634516/bin/antigravity-server

90553e2afa56b5f21a3a7409: start

exitCode==0==

listeningOn==37417==

connectionToken==507312017257==

logFile==/home/vscode/.antigravity-server/.1504c8cc4b34dbfbb4a97ebe954b3da2b5634516.log==

osReleaseId==debian==

arch==x86_64==

platform==linux==

tmpDir==/tmp==

90553e2afa56b5f21a3a7409: end

[Info - 14:02:55.694] Finished installing remote server in container. Output: Waiting for lock...

Lock acquired, proceeding with installation.

Server script already installed in /home/vscode/.antigravity-server/bin/1.16.5-1504c8cc4b34dbfbb4a97ebe954b3da2b5634516/bin/antigravity-server

Server script is already running /home/vscode/.antigravity-server/bin/1.16.5-1504c8cc4b34dbfbb4a97ebe954b3da2b5634516/bin/antigravity-server

90553e2afa56b5f21a3a7409: start

exitCode==0==

listeningOn==37417==

connectionToken==507312017257==

logFile==/home/vscode/.antigravity-server/.1504c8cc4b34dbfbb4a97ebe954b3da2b5634516.log==

osReleaseId==debian==

arch==x86_64==

platform==linux==

tmpDir==/tmp==

90553e2afa56b5f21a3a7409: end

[Info - 14:02:55.799] forwardSocket stdout: forwarder: ====socketForward=success====

[Info - 14:02:55.800] Forwarding port 37417 for container 65e370dba477c5a9e46677d30c5b1ec833696f9200e22a3971fca14c99868062

[Info - 14:02:55.899] forwardPort stdout: forwarder: ====forwarderPort=33761====

[Info - 14:02:55.899] Found forwarder port: 33761

[Error - 14:02:56.299] forwardSocket stderr: forwarder error: handleClient Error: subprocess terminated immediately with return code 127

[Error - 14:02:56.433] forwardPort stderr: forwarder error: handleClient Error: subprocess terminated immediately with return code 127

[Error - 14:02:56.946] forwardPort stderr: forwarder error: handleClient Error: subprocess terminated immediately with return code 127

```

---

<div class="post-metadata">

**Author:** ![Matthew\_Fisch](https://d1dlmcr85iqnpo.cloudfront.net/user_avatar/discuss.ai.google.dev/matthew_fisch/32/84505_2.png) [@Matthew\_Fisch](https://discuss.ai.google.dev/u/Matthew_Fisch)\
**Post date:** [February 5, 2026, 3:01pm UTC](https://discuss.ai.google.dev/t/can-no-longer-connect-to-devcontainer-after-updating-to-v1-16-5/121479/2 "2026-02-05T15:01:01Z")

</div>

… still going strong with SSH remotes

---

<div class="post-metadata">

**Author:** ![Imraj\_Singh](https://d1dlmcr85iqnpo.cloudfront.net/user_avatar/discuss.ai.google.dev/imraj_singh/32/24644_2.png) [@Imraj\_Singh](https://discuss.ai.google.dev/u/Imraj_Singh)\
**Post date:** [February 5, 2026, 5:54pm UTC](https://discuss.ai.google.dev/t/can-no-longer-connect-to-devcontainer-after-updating-to-v1-16-5/121479/3 "2026-02-05T17:54:32Z")

</div>

Updated today and I have the exact same errors with my devcontainers

---

<div class="post-metadata">

**Author:** ![Alexander\_Roiatchki](https://d1dlmcr85iqnpo.cloudfront.net/user_avatar/discuss.ai.google.dev/alexander_roiatchki/32/90744_2.png) [@Alexander\_Roiatchki](https://discuss.ai.google.dev/u/Alexander_Roiatchki)\
**Post date:** [February 5, 2026, 5:56pm UTC](https://discuss.ai.google.dev/t/can-no-longer-connect-to-devcontainer-after-updating-to-v1-16-5/121479/4 "2026-02-05T17:56:26Z")

</div>

I managed to downgrade back to 1.15 on Fedora and now I can use them again, but this isn’t ideal cause some extensions start notifying about updating Antigravity + there’s no way to know if Google might decide to drop support for this version and then I won’t be able to log in and use it.

---

<div class="post-metadata">

**Author:** ![Imraj\_Singh](https://d1dlmcr85iqnpo.cloudfront.net/user_avatar/discuss.ai.google.dev/imraj_singh/32/24644_2.png) [@Imraj\_Singh](https://discuss.ai.google.dev/u/Imraj_Singh)\
**Post date:** [February 5, 2026, 6:14pm UTC](https://discuss.ai.google.dev/t/can-no-longer-connect-to-devcontainer-after-updating-to-v1-16-5/121479/5 "2026-02-05T18:14:46Z")

</div>

Thanks, I think this may trigger my migration back to vscode… Also, I imagine developers of the extensions will prioritise ensuring it works on vscode rather than antigravity.

---

<div class="post-metadata">

**Author:** ![KipK](https://d1dlmcr85iqnpo.cloudfront.net/user_avatar/discuss.ai.google.dev/kipk/32/91036_2.png) [@KipK](https://discuss.ai.google.dev/u/KipK)\
**Post date:** [February 5, 2026, 9:54pm UTC](https://discuss.ai.google.dev/t/can-no-longer-connect-to-devcontainer-after-updating-to-v1-16-5/121479/6 "2026-02-05T21:54:54Z")

</div>

Same problem here since latest update. Can’t even roll back to previous version as you’ve blocked it.  
So can’t even work with antigravity anymore.

Don’t you test builds before release at google ?

---

<div class="post-metadata">

**Author:** ![Abhijit\_Pramanik](https://d1dlmcr85iqnpo.cloudfront.net/user_avatar/discuss.ai.google.dev/abhijit_pramanik/32/32083_2.png) [@Abhijit\_Pramanik](https://discuss.ai.google.dev/u/Abhijit_Pramanik)\
**Post date:** [February 6, 2026, 12:09am UTC](https://discuss.ai.google.dev/t/can-no-longer-connect-to-devcontainer-after-updating-to-v1-16-5/121479/7 "2026-02-06T00:09:07Z")

</div>

Thank you for the report. This has been escalated to our engineering team for investigation.

To provide our developers with the necessary diagnostic data, we encourage you to use the in-app feedback tool (found via the Feedback icon in the top-right corner \> Report Issue). This is the most efficient way to ensure a prompt resolution.

---

<div class="post-metadata">

**Author:** ![Ashwin\_Krishnan](https://d1dlmcr85iqnpo.cloudfront.net/user_avatar/discuss.ai.google.dev/ashwin_krishnan/32/75748_2.png) [@Ashwin\_Krishnan](https://discuss.ai.google.dev/u/Ashwin_Krishnan)\
**Post date:** [February 6, 2026, 4:14pm UTC](https://discuss.ai.google.dev/t/can-no-longer-connect-to-devcontainer-after-updating-to-v1-16-5/121479/8 "2026-02-06T16:14:24Z")

</div>

I was really frustrated with this issue, too. I spent the better part of the last 2 days trying to find the problem

Had Gemini to summarise the bug, cause and a potential hack until Google fixes this properly  
Have still not managed to get Docker in Docker working, though

Hope it helps some of you.

**Summary**

Antigravity version 1.16.5 fails to connect to dev containers with

forwardSocket/ **forwardPort** subprocess exit code 127 (“command not found”). The root cause is a path mismatch in the`getRemoteServerNodePath`function.

## **Environment**

- **Antigravity Version** : 1.16.5 (commit `1504c8cc4b34dbfbb4a97ebe954b3da2b5634516`)

- **OS** : macOS (also likely affects Linux)

- **Container** : Debian-based devcontainer (aarch64)

## **Symptoms**

```auto
forwarder error: handleClient Error: subprocess terminated immediately with return code 127

```

WebSocket close with status code 1006

## **Root Cause**

The `getRemoteServerNodePath` function in `antigravity-dev-containers` extension constructs an **incorrect path** to the remote node binary.

### **The Bug**

**Location** :

antigravity-dev-containers/dist/extension.js→`getRemoteServerNodePath()`

```javascript

// Buggy code (deobfuscated):

getRemoteServerNodePath(output) {

const parsed = this.getRemoteServerHomeAndCommitHash(output);

return `${parsed.serverHome}/bin/${parsed.commitHash}/node`;

// ^^^^^^^^^^^^^^^^^^

// Missing ideVersion prefix!

}

```

**Expected path** : `/home/user/.antigravity-server/bin/1.16.5-{commitHash}/node`  
**Actual path constructed** : `/home/user/.antigravity-server/bin/{commitHash}/node`

The server installation script (`generateBashInstallScript`) installs to:

```bash
SERVER_DIR="$SERVER_DATA_DIR/bin/$DISTRO_IDE_VERSION-$DISTRO_ID"

# e.g., .antigravity-server/bin/1.16.5-1504c8cc4b34.../

```

But `getRemoteServerNodePath` omits the `$DISTRO_IDE_VERSION-` prefix when reconstructing the path.

### **Verification**

```bash
 #Path WITHOUT version prefix - DOES NOT EXIST

docker exec <container> test -f ~/.antigravity-server/bin/1504c8cc4b34.../node

# Result: NOT FOUND

# Path WITH version prefix - EXISTS

docker exec <container> test -f ~/.antigravity-server/bin/1.16.5-1504c8cc4b34.../node

# Result: EXISTS

```

## **Suggested Fix**

Update `getRemoteServerNodePath` to include the IDE version in the path:

```javascript
getRemoteServerNodePath(output) {

const parsed = this.getRemoteServerHomeAndCommitHash(output);

if (!parsed) return null;

// Fix: Include ideVersion prefix in path

return `${parsed.serverHome}/bin/${parsed.ideVersion}-${parsed.commitHash}/node`;

}

getRemoteServerHomeAndCommitHash(output) {

// Update regex to capture ideVersion as well

const match = output.match(/logFile==(.+?\/\.[^\/]+)\/\.([a-f0-9]{40}(?:-dev)?)\.log==/);

if (!match) return null;

// Also parse ideVersion from the output

const ideVersionMatch = output.match(/ideVersion==([^=]+)==/);

return {

        serverHome: match[1],

        commitHash: match[2],

        ideVersion: ideVersionMatch ? ideVersionMatch[1] : this.getIdeVersion()

    };

}

```

## **Workaround**

Add this to your devcontainer’s

postCreate command to create symlinks:

```bash
# Antigravity server symlink workaround

# Bug: Antigravity looks for node at .../bin/{commit}/node

# but server installs to .../bin/{version}-{commit}/node

(

	SERVER_DIR="$HOME/.antigravity-server/bin"

	mkdir -p "$SERVER_DIR"

while true; do

for dir in "$SERVER_DIR"/*-*; do

if [-d "$dir"]; then

				dirname=$(basename "$dir")

				commit="${dirname#*-}"

				symlink="$SERVER_DIR/$commit"

if [! -e "$symlink"]; then

					ln -s "$dir" "$symlink" 2>/dev/null &&

						echo "Antigravity workaround: Created symlink $commit -> $dirname"

fi

fi

done

		sleep 5

done

) >/dev/null 2>&1 &

```

For an existing container, run manually:

```bash
docker exec -u <user> <container> ln -s \

~/.antigravity-server/bin/1.16.5-<commit> \

~/.antigravity-server/bin/<commit>

```

* * *

_Discovered on 2026-02-06. Affects Antigravity 1.16.5. Previous versions may not be affected if they used a different path structure._

---

<div class="post-metadata">

**Author:** ![Muhammad\_Nisar](https://d1dlmcr85iqnpo.cloudfront.net/user_avatar/discuss.ai.google.dev/muhammad_nisar/32/71491_2.png) [@Muhammad\_Nisar](https://discuss.ai.google.dev/u/Muhammad_Nisar)\
**Post date:** [February 6, 2026, 10:49pm UTC](https://discuss.ai.google.dev/t/can-no-longer-connect-to-devcontainer-after-updating-to-v1-16-5/121479/9 "2026-02-06T22:49:59Z")

</div>

> [@Can no longer connect to devcontainer after updating to v1.16.5](https://discuss.ai.google.dev/t/can-no-longer-connect-to-devcontainer-after-updating-to-v1-16-5/121479/7):
>
> Thank you for the report. This has been escalated to our engineering team for investigation. To provide our developers with the necessary diagnostic data, we encourage you to use the in-app feedback tool (found via the Feedback icon in the top-right corner \> Report Issue). This is the most efficient way to ensure a prompt resolution.

---

<div class="post-metadata">

**Author:** ![xNeo](https://d1dlmcr85iqnpo.cloudfront.net/user_avatar/discuss.ai.google.dev/xneo/32/82172_2.png) [@xNeo](https://discuss.ai.google.dev/u/xNeo)\
**Post date:** [February 7, 2026, 2:55am UTC](https://discuss.ai.google.dev/t/can-no-longer-connect-to-devcontainer-after-updating-to-v1-16-5/121479/10 "2026-02-07T02:55:01Z")

</div>

I can confirm this worked for me, thanks!

---

<div class="post-metadata">

**Author:** ![against\_vegetables](https://d1dlmcr85iqnpo.cloudfront.net/user_avatar/discuss.ai.google.dev/against_vegetables/32/91044_2.png) [@against\_vegetables](https://discuss.ai.google.dev/u/against_vegetables)\
**Post date:** [February 8, 2026, 6:57pm UTC](https://discuss.ai.google.dev/t/can-no-longer-connect-to-devcontainer-after-updating-to-v1-16-5/121479/11 "2026-02-08T18:57:33Z")

</div>

Is there any update? This is a critical bug.

Regarding the reports from the IDE: there’s no feedback at all - it looks like the report just disappears into the void. That’s why I have to write here.

---

<div class="post-metadata">

**Author:** ![lgonzalez](https://d1dlmcr85iqnpo.cloudfront.net/user_avatar/discuss.ai.google.dev/lgonzalez/32/23596_2.png) [@lgonzalez](https://discuss.ai.google.dev/u/lgonzalez)\
**Post date:** [February 8, 2026, 10:33pm UTC](https://discuss.ai.google.dev/t/can-no-longer-connect-to-devcontainer-after-updating-to-v1-16-5/121479/12 "2026-02-08T22:33:59Z")

</div>

it works for me also! -10% cortisol.

Thanks @Ashwin_Krishnan !

---

<div class="post-metadata">

**Author:** ![Alexander\_Roiatchki](https://d1dlmcr85iqnpo.cloudfront.net/user_avatar/discuss.ai.google.dev/alexander_roiatchki/32/90744_2.png) [@Alexander\_Roiatchki](https://discuss.ai.google.dev/u/Alexander_Roiatchki)\
**Post date:** [February 10, 2026, 6:44am UTC](https://discuss.ai.google.dev/t/can-no-longer-connect-to-devcontainer-after-updating-to-v1-16-5/121479/13 "2026-02-10T06:44:17Z")

</div>

Thanks for sharing this! The manual fix worked for me but couldn’t quite make it work with the postCreate command. Still, this finally let me use the newest version of agy. I hope Google will start implementing some type of hotfixes for serious issues like this that seem to have relatively easy resolutions.

---

<div class="post-metadata">

**Author:** ![Ivan\_Antonijevic](https://d1dlmcr85iqnpo.cloudfront.net/user_avatar/discuss.ai.google.dev/ivan_antonijevic/32/93813_2.png) [@Ivan\_Antonijevic](https://discuss.ai.google.dev/u/Ivan_Antonijevic)\
**Post date:** [February 16, 2026, 11:25am UTC](https://discuss.ai.google.dev/t/can-no-longer-connect-to-devcontainer-after-updating-to-v1-16-5/121479/14 "2026-02-16T11:25:04Z")

</div>

Thank you @Ashwin_Krishnan you save my day.

---

<div class="post-metadata">

**Author:** ![KipK](https://d1dlmcr85iqnpo.cloudfront.net/user_avatar/discuss.ai.google.dev/kipk/32/91036_2.png) [@KipK](https://discuss.ai.google.dev/u/KipK)\
**Post date:** [February 16, 2026, 6:58pm UTC](https://discuss.ai.google.dev/t/can-no-longer-connect-to-devcontainer-after-updating-to-v1-16-5/121479/15 "2026-02-16T18:58:07Z")

</div>

Still bugged with container from mid january.  
I’ve reported the bug to google on many different communication channels. No feedbcak. No hot fixes.  
Google team, you can’t lag behinds like this for paying customers.  
There’s already enough complains about silly black box quotas, we deserve at least to have proper working tools to work with.

---

<div class="post-metadata">

**Author:** ![Martijn\_Heiden](https://d1dlmcr85iqnpo.cloudfront.net/user_avatar/discuss.ai.google.dev/martijn_heiden/32/94734_2.png) [@Martijn\_Heiden](https://discuss.ai.google.dev/u/Martijn_Heiden)\
**Post date:** [February 19, 2026, 9:07am UTC](https://discuss.ai.google.dev/t/can-no-longer-connect-to-devcontainer-after-updating-to-v1-16-5/121479/16 "2026-02-19T09:07:21Z")

</div>

Could someone confirm of this bug still exists in the new version that came out today?

---

<div class="post-metadata">

**Author:** ![Tamer\_Gezici](https://d1dlmcr85iqnpo.cloudfront.net/user_avatar/discuss.ai.google.dev/tamer_gezici/32/26145_2.png) [@Tamer\_Gezici](https://discuss.ai.google.dev/u/Tamer_Gezici)\
**Post date:** [February 19, 2026, 9:49am UTC](https://discuss.ai.google.dev/t/can-no-longer-connect-to-devcontainer-after-updating-to-v1-16-5/121479/17 "2026-02-19T09:49:49Z")

</div>

After the recent update it seems like it’s fixed. I just tried attaching to a docker container and it worked for me.

---

<div class="post-metadata">

**Author:** ![Martijn\_Heiden](https://d1dlmcr85iqnpo.cloudfront.net/user_avatar/discuss.ai.google.dev/martijn_heiden/32/94734_2.png) [@Martijn\_Heiden](https://discuss.ai.google.dev/u/Martijn_Heiden)\
**Post date:** [February 19, 2026, 10:16am UTC](https://discuss.ai.google.dev/t/can-no-longer-connect-to-devcontainer-after-updating-to-v1-16-5/121479/18 "2026-02-19T10:16:11Z")

</div>

Thank you 🙂 I will update then aswell 🙂

---

<div class="post-metadata">

**Author:** ![Martijn\_Heiden](https://d1dlmcr85iqnpo.cloudfront.net/user_avatar/discuss.ai.google.dev/martijn_heiden/32/94734_2.png) [@Martijn\_Heiden](https://discuss.ai.google.dev/u/Martijn_Heiden)\
**Post date:** [February 19, 2026, 10:40am UTC](https://discuss.ai.google.dev/t/can-no-longer-connect-to-devcontainer-after-updating-to-v1-16-5/121479/19 "2026-02-19T10:40:14Z")

</div>

After an upgrade and a docker rebuild the problem still very much persists. I’m going back to v1.15 again..

---

<div class="post-metadata">

**Author:** ![Tamer\_Gezici](https://d1dlmcr85iqnpo.cloudfront.net/user_avatar/discuss.ai.google.dev/tamer_gezici/32/26145_2.png) [@Tamer\_Gezici](https://discuss.ai.google.dev/u/Tamer_Gezici)\
**Post date:** [February 19, 2026, 11:49am UTC](https://discuss.ai.google.dev/t/can-no-longer-connect-to-devcontainer-after-updating-to-v1-16-5/121479/20 "2026-02-19T11:49:06Z")

</div>

Sorry to hear! I must note that I updated my Antigravity by downloading the new installer from the website and installing it again without uninstalling my previous installation. If that makes a difference.

[Next page](https://discuss.ai.google.dev/t/can-no-longer-connect-to-devcontainer-after-updating-to-v1-16-5/121479.md?page=2)