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
@@ -240,25 +244,25 @@ Simply define the additional images in the `images` configuration option.
240
244
241
245
Here are the supported formats for `import.copacetic.buildkit.addr` configuration option:
242
246
243
-
* `unix:///path/to/buildkit.sock` - Connect to buildkit over unix socket.
244
-
* `tcp://$BUILDKIT_ADDR:$PORT` - Connect to buildkit over TCP. (not recommended for security reasons)
245
-
* `docker://<docker connection spec>` - Connect to docker, currently only unix sockets are supported, e.g. `docker://unix:///var/run/docker.sock` (or just `docker://`).
246
-
* `docker-container://my-buildkit-container` - Connect to a buildkitd running in a docker container.
247
-
* `buildx://my-builder` - Connect to a buildx builder (or `buildx://` for the currently selected builder). *Note: only container-backed buildx instances are currently supported*
248
-
* `nerdctl-container://my-container-name` - Similar to `docker-container` but uses `nerdctl`.
249
-
* `podman-container://my-container-name` - Similar to `docker-container` but uses `podman`.
250
-
* `ssh://myhost` - Connect to a buildkit instance over SSH. Format of the host spec should mimic the SSH command.
251
-
* `kubepod://mypod` - Connect to buildkit running in a Kubernetes pod. Can also specify kubectl context and pod namespace (`kubepod://mypod?context=foo&namespace=notdefault`).
247
+
-`unix:///path/to/buildkit.sock`- Connect to buildkit over unix socket.
248
+
-`tcp://$BUILDKIT_ADDR:$PORT`- Connect to buildkit over TCP. (not recommended for security reasons)
249
+
-`docker://<docker connection spec>`- Connect to docker, currently only unix sockets are supported, e.g. `docker://unix:///var/run/docker.sock` (or just `docker://`).
250
+
-`docker-container://my-buildkit-container`- Connect to a buildkitd running in a docker container.
251
+
-`buildx://my-builder` - Connect to a buildx builder (or `buildx://` for the currently selected builder). *Note: only container-backed buildx instances are currently supported*
252
+
-`nerdctl-container://my-container-name`- Similar to `docker-container` but uses `nerdctl`.
253
+
-`podman-container://my-container-name`- Similar to `docker-container` but uses `podman`.
254
+
-`ssh://myhost`- Connect to a buildkit instance over SSH. Format of the host spec should mimic the SSH command.
255
+
-`kubepod://mypod`- Connect to buildkit running in a Kubernetes pod. Can also specify kubectl context and pod namespace (`kubepod://mypod?context=foo&namespace=notdefault`).
252
256
253
257
See more details in the [Copacetic Documentation](https://project-copacetic.github.io/copacetic/website/custom-address)
254
258
255
259
### mTLS
256
260
257
261
Helmper supports setting required configuration options for enabling mTLS with an expose Buildkit instance over TCP, although the following configuration options:
258
262
259
-
* `import.copacetic.buildkitd.CACertPath`
260
-
* `import.copacetic.buildkitd.certPath`
261
-
* `import.copacetic.buildkitd.keyPath`
263
+
-`import.copacetic.buildkitd.CACertPath`
264
+
-`import.copacetic.buildkitd.certPath`
265
+
-`import.copacetic.buildkitd.keyPath`
262
266
263
267
Read more in the official docs by [moby/buildkit](https://github.com/moby/buildkit?tab=readme-ov-file#expose-buildkit-as-a-tcp-service).
0 commit comments