You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Switch buildx remote driver from TCP to docker-container
Replace tcp://localhost:1234 endpoint with docker-container://buildcage.
This eliminates the need for TCP port exposure and simplifies the connection between buildx and the builder container.
| `allowed_https_rules` | No | empty | HTTPS allow rules (wildcard or regex, port required) |
194
195
| `allowed_http_rules` | No | empty | HTTP allow rules (wildcard or regex, port required) |
195
196
| `allowed_ip_rules` | No | empty | IP address allow rules (wildcard or regex, port required) |
196
-
| `port` | No | `1234` | BuildKit endpoint port on localhost |
197
197
198
198
**Rule syntax**
199
199
@@ -210,20 +210,16 @@ IP address rules (e.g., `192.168.1.1:443`) use the same syntax but go in `allowe
210
210
211
211
For detailed syntax, see [Rule Syntax](./docs/rules.md).
212
212
213
-
#### Outputs
213
+
#### Connecting Buildx
214
214
215
-
| Name | Description |
216
-
|------|-------------|
217
-
| `port` | BuildKit endpoint port |
218
-
219
-
Pass this port to [`docker/setup-buildx-action`](https://github.com/docker/setup-buildx-action) to use Buildcage as a remote builder:
215
+
Pass the container name to [`docker/setup-buildx-action`](https://github.com/docker/setup-buildx-action) to use Buildcage as a remote builder. The `endpoint` must match the `builder_name` parameter (default: `buildcage`):
0 commit comments