# [BUG] Dev Container: Remote server installation fails silently
## Summary
When attempting to connect to a dev container in Antigravity, the remote server installation fails with a generic error. The **exact same dev container configuration works perfectly in VS Code**, indicating this is an Antigravity-specific issue.
## Environment
- **Antigravity Version**: 1.11.9 (commit: b31a0ea425328717c6bd1cff12c6755fd3d63a9d)
- **OS**: Ubuntu 22.04.1 LTS (Linux 6.8.0-87-generic x86_64)
- **Docker**: 29.1.1
- **Docker Compose**: v2.15.1
- **Container Base**: ruby:3.4.7-slim (Debian 13 Trixie)
## Steps to Reproduce
1. Create a dev container with the following configuration:
**`.devcontainer/devcontainer.json`**:
```json
{
“name”: “MyApp (Rails dev)”,
“dockerComposeFile”: [“docker-compose.yml”],
“service”: “web”,
“workspaceFolder”: “/rails”,
“features”: {
" Package features/github-cli · GitHub ": {},
" Package features/common-utils · GitHub ": {}
}
}
```
**`.devcontainer/docker-compose.yml`**:
```yaml
services:
web:
image: my_app-web
ports:
- "3000:3000"
volumes:
- ..:/rails
- bundle_cache:/usr/local/bundle
environment:
RAILS_ENV: development
command: /bin/sh -c “rm -f tmp/pids/server.pid && ./bin/rails server -b 0.0.0.0”
volumes:
bundle_cache:
```
**`Dockerfile.dev`**:
```dockerfile
ARG RUBY_VERSION=3.4.7
FROM Docker Hub Container Image Library | App Containerization
WORKDIR /rails
RUN apt-get update -qq && \
apt-get install --no-install-recommends -y curl wget libjemalloc2 libvips sqlite3 build-essential git libyaml-dev pkg-config && \\
rm -rf /var/lib/apt/lists /var/cache/apt/archives
ENV RAILS_ENV=“development” \
BUNDLE_PATH="/usr/local/bundle"
COPY Gemfile Gemfile.lock ./
RUN bundle install
COPY . .
ENTRYPOINT [“/rails/bin/docker-entrypoint”]
EXPOSE 3000
CMD [“./bin/rails”, “server”, “-b”, “0.0.0.0”]
```
2. Build the image: `docker build -f Dockerfile.dev -t my_app-web .`
3. Start the dev container in Antigravity
4. Observe the error
## Expected Behavior
The dev container should start successfully and Antigravity should connect to the remote server inside the container (like VS Code does).
## Actual Behavior
Connection fails with:
```
[Error - 18:12:46.814] Error executing command: Command failed: docker exec -e SSH_AUTH_SOCK=/tmp/antigravity-remote-ssh-a39786bfeaa47755ef400a96.sock -u root 8da905906dc54c6c91b562b3bf8a523ce8274f7b826c8afc1007b7db4c126df3 bash /tmp/a39786bfeaa47755ef400a96.sh
[Error - 18:12:46.814] stdout: Waiting for lock…
Lock acquired, proceeding with installation.
[Error - 18:12:46.815] Failed to install remote server in container
```
## Investigation
I’ve verified that:
Container runs correctly
`wget` is installed (`/usr/bin/wget`)
Network connectivity works
Antigravity server download URL is accessible
**Manual installation works perfectly**:
```bash
docker exec container-web-1 bash -c “mkdir -p /root/.antigravity-server/bin/b31a0ea425328717c6bd1cff12c6755fd3d63a9d && cd /root/.antigravity-server/bin/b31a0ea425328717c6bd1cff12c6755fd3d63a9d && wget --tries=3 --timeout=10 --quiet -O vscode-server.tar.gz ‘https://edgedl.me.gvt1.com/edgedl/release2/j0qc3/antigravity/stable/1.11.9-b31a0ea425328717c6bd1cff12c6755fd3d63a9d/linux-x64/Antigravity-reh.tar.gz’ && tar -xf vscode-server.tar.gz --strip-components 1 && rm -f vscode-server.tar.gz”
```
This succeeds and extracts the server correctly.
## Key Observation
**The exact same dev container configuration works perfectly in VS Code**
This strongly suggests an Antigravity-specific issue with the dev container integration or the server installation script.
## Additional Notes
The installation script acquires the lock successfully (“Lock acquired, proceeding with installation.”) but then **fails silently without any meaningful error message**, making it very difficult to debug.
## Workaround
Currently using VS Code for dev container development.
## Impact
This prevents using Antigravity with dev containers, which is critical for modern containerized development workflows.
-–
## Full Logs
Click to expand complete logs
```
[Info - 18:12:44.449] Resolving dev container authority…
[Info - 18:12:44.450] Starting Antigravity Dev Containers…
[Info - 18:12:44.520] Docker version: 29.1.1
[2025-11-29T18:12:44.849Z] @devcontainers/cli 0.72.0. Node.js v22.18.0
[2025-11-29T18:12:45.054Z] Start: Resolving Remote
[2025-11-29T18:12:45.790Z] Stop (736 ms): Resolving Remote
[Info - 18:12:45.801] Found container ID: 8da905906dc54c6c91b562b3bf8a523ce8274f7b826c8afc1007b7db4c126df3
[Info - 18:12:46.341] Remote user: root
[Info - 18:12:46.341] Installing remote server in container…
[Info - 18:12:46.665] SSH Agent Forwarding: true
[Error - 18:12:46.814] Error executing command: Command failed: docker exec -e SSH_AUTH_SOCK=/tmp/antigravity-remote-ssh-a39786bfeaa47755ef400a96.sock -u root 8da905906dc54c6c91b562b3bf8a523ce8274f7b826c8afc1007b7db4c126df3 bash /tmp/a39786bfeaa47755ef400a96.sh
Command: docker exec -e SSH_AUTH_SOCK=/tmp/antigravity-remote-ssh-a39786bfeaa47755ef400a96.sock -u root 8da905906dc54c6c91b562b3bf8a523ce8274f7b826c8afc1007b7db4c126df3 bash /tmp/a39786bfeaa47755ef400a96.sh
[Error - 18:12:46.814] stdout: Waiting for lock…
Lock acquired, proceeding with installation.
[Error - 18:12:46.815] Failed to install remote server in container: Error: Command failed: docker exec -e SSH_AUTH_SOCK=/tmp/antigravity-remote-ssh-a39786bfeaa47755ef400a96.sock -u root 8da905906dc54c6c91b562b3bf8a523ce8274f7b826c8afc1007b7db4c126df3 bash /tmp/a39786bfeaa47755ef400a96.sh
```
-–
**Has anyone else experienced this issue? Any suggestions for debugging or workarounds?**
-–
_Note: This issue was debugged and documented with assistance from Antigravity AI, which helped identify the root cause through systematic testing (verifying wget availability, network connectivity, manual server installation, etc.) and create this comprehensive bug report._