feat(sandbox): add GCE metadata emulator for Google Cloud

[p5]

Summary

Right now you can't use Google Cloud APIs (Vertex AI, Cloud Storage, BigQuery, Drive, Maps, etc.) from inside a sandbox. GCP SDKs expect a metadata server to be running and query it to get tokens - but there's no metadata server in the sandbox, so they fail before any API call is even attempted.

Go's metadata client makes this worse. It dials the metadata IP directly over TCP, bypassing HTTP_PROXY entirely, so the sandbox proxy never even sees the request. Additionally, there's no way to override this from within the SDK config.

This PR adds a google-cloud provider type and a GCE metadata emulator running on loopback (127.0.0.1:8174) inside the sandbox network namespace. GCP SDKs find it via GCE_METADATA_HOST, get credential placeholders back, and include those in their API calls. The proxy resolves placeholders to real tokens at egress. The sandbox process never holds a real credential.

Related Issue

Closes #1706

Changes

• Add google_cloud module with shared constants and loopback address
• Add google_cloud_metadata module implementing GCE metadata API
• Add metadata_server module with MetadataHandler trait for provider- agnostic loopback server lifecycle
• Add child_env_resolved() and gcp_token_response() for GCP-aware credential state
• Bind via std::thread::spawn + setns (not spawn_blocking) to avoid tokio thread pool namespace contamination
• Start metadata server before SSH handler to ensure consistent env on bind failure
• Add google-cloud.yaml provider profile and credentials documentation

Testing

• mise run pre-commit passes
• Unit tests added/updated
• E2E tests added/updated (if applicable)

Checklist

• Follows Conventional Commits
• Commits are signed off (DCO)
• Architecture docs updated (if applicable)

[copy-pr-bot]

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

[github-actions]

All contributors have signed the DCO ✍️ ✅
_{Posted by the DCO Assistant Lite bot.}

[p5]

I have read the DCO document and I hereby sign the DCO.

[github-actions]

Label test:e2e applied, but pull-request/1763 is at {"messa while the PR head is 28d626a. A maintainer needs to comment /ok to test 28d626a9e068293469bbeb1661bdb77e973112df to refresh the mirror. Once the mirror catches up, re-run Branch E2E Checks from the Actions tab.

[maxamillion]

/ok to test 28d626a

[p5]

Force pushed to fix the lint issues. "mise run pre-commit" now succeeds locally again.

Previous E2E tests ongoing here - https://github.com/NVIDIA/OpenShell/actions/runs/26982657920

---

Edit:
rust-docker E2E tests failed. It looks like a flake, especially given the same tests for podman are passing.

[maxamillion]

This is great! One nit pick though, I think GCE_METADATA_IP should include the emulator port. The google-auth python library builds its metadata ping URL directly from GCE_METADATA_IP, so 127.0.0.1 becomes http://127.0.0.1 on port 80 but the shim listens on 127.0.0.1:8174 ... from an initial check, it looks like the other language libraries for google auth use GCE_METADATA_HOST

Tested with:

$ env UV_CACHE_DIR=/tmp/uv-cache uv run --with google-auth --with requests python /tmp/verify_gce_metadata_ip.py
ping_127_no_port False
ping_127_with_port True

here's the contents of /tmp/verify_gce_metadata_ip.py:

import os
import threading
import http.server
import socketserver

import google.auth.compute_engine._metadata as metadata
from google.auth.transport.requests import Request


class MetadataHandler(http.server.BaseHTTPRequestHandler):
    def do_GET(self):
        self.send_response(200)
        self.send_header("Metadata-Flavor", "Google")
        self.end_headers()

    def log_message(self, *args):
        pass


def main():
    server = socketserver.TCPServer(("127.0.0.1", 8174), MetadataHandler)
    thread = threading.Thread(target=server.serve_forever, daemon=True)
    thread.start()

    try:
        request = Request()

        os.environ["GCE_METADATA_IP"] = "127.0.0.1"
        print("ping_127_no_port", metadata.ping(request, timeout=1, retry_count=1))

        os.environ["GCE_METADATA_IP"] = "127.0.0.1:8174"
        print("ping_127_with_port", metadata.ping(request, timeout=1, retry_count=1))
    finally:
        server.shutdown()
        server.server_close()


if __name__ == "__main__":
    main()

[p5]

Awesome spot!
You're correct - the variable should include the port.

Ran through your reproducer and confirmed it now works as expected.

[cgwalters]

One thing I'd like to consider here is OpenShell including something like https://github.com/LobsterTrap/llmproxy by default - i.e. an inference endpoint that always appears to be OpenResponses compatible to inner tooling. Wouldn't work with Claude Code (AFAIK without hacks) but it'd be nice to just entirely remove needing to handle inference provider auth at all for all the tools that can speak OpenResponses.

It's a heavier hammer here though.

Of course it's worth noting that many non-local deployments will probably end up wanting some kind of proxy anyways to handle observability etc. There's various existing more heavyweight things in that space.

[stbenjam]

Thanks, these changes work for me standalone following Adam's instructions.

Will vertex provider stay or get stripped out? It might be confusing if it exists but doesn't work with CC.

[TaylorMutch]

/ok to test aada3da

[p5]

Will vertex provider stay or get stripped out? It might be confusing if it exists but doesn't work with CC.

It's out of scope for this PR to deprecate the original vertex provider, nor does this PR label itself as an inference provider - even though it can be used in that way.

There are discussions ongoing as to whether the original should be deprecated. There are pros and cons for each.
The Google Cloud provider (this PR) gives OpenShell less visibility into inference as requests do not go through inference.local, but does provide more seamless use of Google SDKs in coding agents (#1752 wouldn't have been needed with this).

if it exists but doesn't work with CC.

Was this a regression from my PR? CC should remain working with the original provider following the merge of #1752.

[stbenjam]

This PR gives the foundation to let inference.local work without needing the complicated L7 translation layer, and there are lots of benefits to that. I agree its out of scope to do more to the vertex provider here.

if it exists but doesn't work with CC.
Was this a regression from my PR? CC should remain working with the original provider following the merge of #1752.

No it wasn't clear to me that 1752 was going to land.

This PR works well for me, thanks.

[maxamillion]

/ok to test 5d6ba08

[maxamillion]

This is great, thank you! I'm a big fan of this approach. 👍

[maxamillion]

/ok to test fa02fe2

[maxamillion]

rerunning failed jobs, it looks like CI timed out trying to talk to ghcr.io