cwielenb/CNCF-Dataset huggingface dataset:
Project: SeaTunnel (App Definition and Development / Streaming & Messaging)
File: Maxcompute.md

Maxcompute source connector Used to read data from Maxcompute. | name | type | required | default value | |-|--|-|| | accessId | string | yes | - | | accesskey | string | yes | - | | endpoint | string | yes | - | | project | string | yes | - | | table_name | string | yes | - | | partition_spec | string | no | - | | split_row | int | no | 10000 | | common-options | string | no | | | schema | config | no | | `accessId` Your Maxcompute accessId which cloud be access from Alibaba Cloud. `accesskey` Your Maxcompute accessKey which cloud be access from Alibaba Cloud. `endpoint` Your Maxcompute endpoint start with http. `project` Your Maxcompute project which is created in Alibaba Cloud. `table_name` Target Maxcompute table name eg: fake. `partition_spec` This spec of Maxcompute partition table eg:ds='20220101'. `split_row` Number of rows per split, default: 10000. Source plugin common parameters, please refer to for details. The schema information of upstream data. ```hocon source { Maxcompute { accessId="<your access id>" accesskey="<your access Key>" endpoint="<http://service.odps.aliyun.com/api>" project="<your project>" table_name="<your table name>" schema { fields { name = string age = int gender = string } } } } ``` ) )
Project: KICS (Provisioning / Security & Compliance)
File: 90501b1b-cded-4cc1-9e8b-206b85cda317.md

title: S3 Static Website Host Enabled hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 90501b1b-cded-4cc1-9e8b-206b85cda317 Query name: S3 Static Website Host Enabled Platform: CloudFormation Severity: <span style="color:#bb2124">High</span> Category: Insecure Configurations URL: Checks if any static websites are hosted on buckets. Even static websites can be a liability when poorly configured.<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="6" Resources: Bucket2: Type: AWS::S3::Bucket Properties: AccessControl: PublicRead WebsiteConfiguration: IndexDocument: index.html ErrorDocument: error.html ``` ```json title="Positive test num. 2 - json file" hl_lines="7" { "Resources": { "Bucket2": { "Type": "AWS::S3::Bucket", "Properties": { "AccessControl": "PublicRead", "WebsiteConfiguration": { "IndexDocument": "index.html", "ErrorDocument": "error.html" } } } } } ``` ```yaml title="Negative test num. 1 - yaml file" Resources: Bucket1: Type: AWS::S3::Bucket Properties: PublicAccessBlockConfiguration: BlockPublicAcls : true BlockPublicPolicy : true IgnorePublicAcls : true RestrictPublicBuckets : true ``` ```json title="Negative test num. 2 - json file" { "Resources": { "Bucket1": { "Type": "AWS::S3::Bucket", "Properties": { "PublicAccessBlockConfiguration": { "BlockPublicAcls": true, "BlockPublicPolicy": true, "IgnorePublicAcls": true, "RestrictPublicBuckets": true }, "AccessControl": "Private" } } } } ```
Project: GraphScope (App Definition and Development / Database)
File: java_tutorials.md

Java plays an important role in big data ecosystem, and a lot of graph processing systems developed by Java (e.g., Apache Giraph and GraphX) have been widely applied. To integrate with Java ecosystem, GraphScope allows graph analytics algorithms developed for Apache Giraph and GraphX to directly run over GraphScope GAE. In addition, GraphScope GAE supports the PIE programming model, which can provide better performance than widely-used vertex-centric model. GraphScope GAE is equipped with `Java PIE` interface exposed by `GRAPE-jdk`, and users can develop their own algorithms using the PIE programming model. The following tutorials will introduce how to leverage the above features in GraphScope GAE Java SDK.
Project: Open Policy Containers (Provisioning / Security & Compliance)
File: MAINTAINERS.md

The following table lists Open Policy Registry (OPCR) project maintainers and areas of expertise in alphabetical order: | Name | GitHub | Email | Organization | Repositories/Area of Expertise | Added/Renewed On | | | | | | | | | Mihai Buzgau | @mihaibuzgau | mihai.buzgau@aserto.com | Aserto | all repositories | 2023-01-18 | | Daniel Carabas | @carabasdaniel | dani@aserto.com | Aserto | all repositories | 2022-12-25 | | Florin Dragos | @florindragos | florin@aserto.com | Aserto | all repositories | 2023-01-18 | | Gert Drapers | @gertd | gert@aserto.com | Aserto | all repositories | 2021-09-28 | | Omri Gazitt | @ogazitt | omri@aserto.com | Aserto | all repositories | 2021-09-28 | | Gheorghe Popescu | @gimmyxd | gheorghe.popescu@aserto.com | Aserto | all repositories | 2023-01-18 | | Vlad Iovanov | @viovanov | vlad@pulley.com | Pulley | all repositories | 2021-09-28 | | Oana Tanasoiu | @oanatmaria | oana@aserto.com | Aserto | all repositories | 2023-01-18 | | Andrew Poland | @apoland | apoland@aserto.com | Aserto | all repositories | 2023-01-18 | | Noa Shavit | @noashavit | noa@aserto.com | Aserto | all repositories | 2023-04-04 |
Project: Vald (App Definition and Development / Database)
File: development.md

This document describes how to set up the development environment and how to develop Vald. When using Docker related environment, you can use any OS that supports Docker. When using native environment, `Linux` is required. `amd64` is recommended because `NGT`, the vector search library we use, is optimized for `amd64`. But you can also build and test `Vald` on `arm64` with the same way as described below. This is the easiest way to start developing `Vald`. You can just open our with `VS Code` and go. We don't officially have a setup documentation for now, but you can take a look at the . That's everything you need to build and test `Vald`, so you can use it as a reference. If you would like to use the `Dockerfile` directlly, please note that `docker-in-docker` environment is required to run our E2E tests. In devcontainer, . The command below will run all the unit tests. ```bash make test ``` The steps below will deploy a Vald cluster to the local `k3d` cluster and run the E2E tests. Change `example/helm/values.yaml` to `dimensions: 784` and `distance_type: l2`. Run the commands below. ```bash make hack/benchmark/assets/dataset/fashion-mnist-784-euclidean.hdf5 make k3d/start make k8s/vald/deploy HELM_VALUES=example/helm/values.yaml make e2e E2EWAITFORCREATEINDEX_DURATION=3m make k8s/vald/delete ```
Project: SOPS (Provisioning / Security & Compliance)
File: release.md

This document describes the procedure for releasing a new version of SOPS. It is intended for maintainers of the project, but may be useful for anyone interested in the release process. The release is performed by creating a signed tag for the release, and pushing it to GitHub. This will automatically trigger a GitHub Actions workflow that builds the binaries, packages, SBOMs, and other artifacts for the release using , and uploads them to GitHub. The configuration for GoReleaser is in the file . The configuration for the GitHub Actions workflow is in the file . This configuration is quite sophisticated, and ensures at least the following: The release is built for multiple platforms and architectures, including Linux, macOS, and Windows, and for both AMD64 and ARM64. The release includes multiple packages in Debian and RPM formats. For every binary, a corresponding SBOM is generated and published. For all binaries, a checksum file is generated and signed using with GitHub OIDC. Both Debian and Alpine Docker multi-arch images are built and pushed to GitHub Container Registry and Quay.io. The container images are signed using with GitHub OIDC. metadata is generated for release artifacts and container images. [ ] Ensure that all changes intended for the release are merged into the `main` branch. At present, this means that all pull requests attached to the milestone for the release are merged. If there are any pull requests that should not be included in the release, move them to a different milestone. file. This should include a summary of all changes since the last release, including references to any relevant pull requests. [ ] In this same pull request, update the version number in `version/version.go` to the new version number. [ ] Get approval for the pull request from at least one other maintainer, and merge it into `main`. [ ] Ensure CI passes on the `main` branch. [ ] Ensure your local copy of the `main` branch is up-to-date: ```sh git checkout main git pull ``` [ ] Create a signed tag for the release, using the following command: ```sh git tag -s -m <version> <version> ``` where `<version>` is the version number of the release. The version number should be in the form `vX.Y.Z`, where `X`, `Y`, and `Z` are integers. The version number should be incremented according to . [ ] Push the tag to GitHub: ```sh git push origin <version> ``` [ ] Ensure the release is built successfully on GitHub Actions. This will automatically create a release on GitHub.
Project: kube-hunter (Provisioning / Security & Compliance)
File: KHV042.md

vid: KHV042 title: Exposed Attaching To Container categories: [Remote Code Execution] severity: high An attacker could attach to a running container via a websocket on the kubelet's `/attach` endpoint. This endpoint is exposed as part of the kubelet's debug handlers. Disable `--enable-debugging-handlers` kubelet flag.
Project: ClickHouse (App Definition and Development / Database)
File: v21.10.4.26-stable.md

sidebar_position: 1 sidebar_label: 2022 Backported in : Improve performance of JSON and XML output formats. (). Backported in : Quota limit was not reached, but the limit was exceeded. This PR fixes . (). Backported in : Remove not like function into RPNElement. (). Backported in : Resolve `nullptr` in STS credentials provider for S3. (). Backported in : Disable `partialmergejoinlefttablebufferbytes` before bug in this optimization is fixed. See ). * Remove redundant option `partialmergejoin_optimizations`. (). Backported in : `RENAME TABLE` query worked incorrectly on attempt to rename an DDL dictionary in `Ordinary` database, it's fixed. (). Backported in : Settings `inputformatallowerrorsnum` and `inputformatallowerrorsratio` did not work for parsing of domain types, such as `IPv4`, it's fixed. Fixes . (). Backported in : Fixed `there are no such cluster here` error on execution of `ON CLUSTER` query if specified cluster name is name of `Replicated` database. (). Backported in : Fix race in JSONEachRowWithProgress output format when data and lines with progress are mixed in output. (). Backported in : Fix group by / order by / limit by aliases with positional arguments enabled. Closes . (). Backported in : Fix usage of `Buffer` table engine with type `Map`. Fixes . (). Backported in : Fix possible assertion `../src/IO/ReadBuffer.h:58: bool DB::ReadBuffer::next(): Assertion '!hasPendingData()' failed.` in TSKV format. (). Backported in : Fix invalid cast of nullable type when nullable primary key is used. This fixes . (). Backported in : Fix a bug about function transform with decimal args. (). Backported in : - Change configuration path from `keeperserver.sessiontimeoutms` to `keeperserver.coordinationsettings.sessiontimeoutms` when constructing a `KeeperTCPHandler` - Same with `operationtimeout`. (). Backported in : Fix functions `empty` and `notEmpty` with arguments of `UUID` type. Fixes . (). Support toUInt8/toInt8 for if constant condition optimization. ().
Project: Sonobuoy (Provisioning / Security & Compliance)
File: gen.md

Sonobuoy provides many flags to customize your run but sometimes you have a special use case that isn't supported yet. For these cases, Sonobuoy provides `sonobuoy gen`. The command `sonobuoy gen` will print the YAML for your run to stdout instead of actually creating it. It accepts all of the relevant flags for customizing the run just like `sonobuoy run` would. You can then edit it yourself and apply it as if Sonobuoy had run it. Output the YAML Sonobuoy would create to a file: ``` sonobuoy gen --e2e-focus="sig-networking" --e2e-skip="Alpha" > sonobuoy.yaml ``` Then manually modify it as necessary. Maybe you need special options for plugins or want your own sidecar to be running with the images. Finally, create the resources yourself via kubectl. ``` sonobuoy run -f sonobuoy.yaml ``` Note: If you find that you need this flow to accomplish your work, talk to us about it in our channel or file an in Github. Others may have the same need and we'd love to help support you.
Project: YDB (App Definition and Development / Database)
File: corr_covar.md

Correlation and covariance between two columns. Abbreviated versions are also available: `CORR` or `COVAR`. For covariance, there are also versions with the `SAMPLE`/`POPULATION` suffix that are similar to above. Unlike most other aggregate functions, they don't skip `NULL`, but accept it as 0. When you use , a `Tuple` containing two values is passed as the first argument. Examples ```yql SELECT CORRELATION(numericcolumn, anothernumeric_column), COVARIANCE(numericcolumn, anothernumeric_column) FROM my_table; ``` ```yql $corr_factory = AggregationFactory("CORRELATION"); SELECT AGGREGATEBY(AsTuple(numericcolumn, anothernumericcolumn), $corr_factory) FROM my_table; ```
Project: YugabyteDB (App Definition and Development / Database)
File: yugabyte-operator.md

title: Open source Kubernetes using YugabyteDB operator headerTitle: Open source Kubernetes linkTitle: Open source Kubernetes description: Deploy a YugabyteDB cluster with a Kubernetes native customer resource. menu: v2.18: parent: deploy-kubernetes-sz name: Open Source identifier: k8s-oss-2 weight: 621 type: docs <ul class="nav nav-tabs-alt nav-tabs-yb"> <li > <a href="../helm-chart/" class="nav-link"> <i class="fa-regular fa-dharmachakra" aria-hidden="true"></i> Helm chart </a> </li> <li > <a href="../yugabyte-operator/" class="nav-link active"> <i class="fa-solid fa-cubes" aria-hidden="true"></i> Kubernetes Operator (legacy) </a> </li> </ul> The Kubernetes Operator for YugabyteDB is no longer maintained. It is recommended that you use the actively maintained for YugabyteDB to install YugabyteDB on Kubernetes. For documentation on using the Kubernetes Operator for YugabyteDB, refer to the . A newer version of the Kubernetes Operator for YugabyteDB is in development.
Project: SeaTunnel (App Definition and Development / Streaming & Messaging)
File: DingTalk.md

DinkTalk sink connector A sink plugin which use DingTalk robot send message | name | type | required | default value | |-|--|-|| | url | string | yes | - | | secret | string | yes | - | | common-options | | no | - | DingTalk robot address format is https://oapi.dingtalk.com/robot/send?access_token=XXXXXXstring DingTalk robot secret (string) Sink plugin common parameters, please refer to for details ```hocon sink { DingTalk { url="https://oapi.dingtalk.com/robot/send?access_token=ec646cccd028d978a7156ceeac5b625ebd94f586ea0743fa501c100007890" secret="SEC093249eef7aa57d4388aa635f678930c63db3d28b2829d5b2903fc1e5c10000" } } ``` Add DingTalk Sink Connector
Project: StarRocks (App Definition and Development / Database)
File: jodatime_format.md

displayed_sidebar: "English" Converts the specified date into a string in the specified Joda DateTimeFormat pattern format. ```Haskell VARCHAR JODATIME_FORMAT(DATETIME | DATE date, VARCHAR format) ``` `date`: the date you want to convert. It must be a valid date or date expression. `format`: the format of the date and time to be returned. For information about the available formats, see . Currently, the return value is a string that contains a maximum of 128 bytes in length. If the length of the string converted from the specified date exceeds 128 bytes, `NULL` is returned. Example 1: Convert the date `2020-06-25 15:58:51` into a string in `yyyy-MM-dd` format. ```SQL MySQL > select jodatime_format('2020-06-25 15:58:51', 'yyyy-MM-dd'); ++ | jodatime_format('2020-06-25 15:58:51', 'yyyy-MM-dd') | ++ | 2020-06-25 | ++ ``` Example 2: Convert the date `2020-06-25 15:58:51` into a string in `yyyy-MM-dd HH:mm:ss` format. ```SQL MySQL > select jodatime_format('2020-06-25 15:58:51', 'yyyy-MM-dd HH:mm:ss'); ++ | jodatime_format('2020-06-25 15:58:51', 'yyyy-MM-dd HH:mm:ss') | ++ | 2020-06-25 15:58:51 | ++ ``` Example 3: Convert the date `2020-06-25 15:58:51` into a string in `MM dd ee EE` format. ```SQL MySQL > select jodatime_format('2020-06-25 15:58:51', 'MM dd ee EE'); +-+ | jodatime_format('2020-06-25 15:58:51', 'MM dd ee EE') | +-+ | 06 25 04 Thu | +-+ ``` Example 4: Convert the date `2020-06-25 15:58:51` into a string in `MMM dd ee EEE` format. ```SQL MySQL > select jodatime_format('2020-06-25 15:58:51', 'MMM dd ee EEE'); ++ | jodatime_format('2020-06-25 15:58:51', 'MMM dd ee EEE') | ++ | Jun 25 04 Thu | ++ ``` Example 5: Convert the date `2020-06-25 15:58:51` into a string in `MMMM dd ee EEEE` format. ```SQL MySQL > select jodatime_format('2020-06-25 15:58:51', 'MMMM dd ee EEEE'); +--+ | jodatime_format('2020-06-25 15:58:51', 'MMMM dd ee EEEE') | +--+ | June 25 04 Thursday | +--+ ``` Example 6: Convert the date `2023-06-25 12:00:00` into a string in `KK:mm:ss a` format. ```SQL MySQL > select jodatime_format('2023-06-25 12:00:00', 'KK:mm:ss a'); ++ | jodatime_format('2023-06-25 12:00:00', 'KK:mm:ss a') | ++ | 00:00:00 PM | ++ ``` Example 7: Convert the date `2023-06-25 12:00:00` into a string in `hh:mm:ss a` format. ```SQL MySQL > select jodatime_format('2023-06-25 12:00:00', 'hh:mm:ss a'); ++ | jodatime_format('2023-06-25 12:00:00', 'hh:mm:ss a') | ++ | 12:00:00 PM | ++ ``` Example 8: Convert the date `2023-06-25 00:00:00` into a string in `yyyyMMdd ''starrocks''` format. ```SQL MySQL > select jodatime_format('2023-06-25 00:00:00', 'yyyyMMdd ''starrocks'''); ++ | jodatime_format('2023-06-25 00:00:00', 'yyyyMMdd \'starrocks\'') | ++ | 20230625 starrocks | ++ ``` JODATIME_FORMAT, JODA, FORMAT
Project: Beam (App Definition and Development / Streaming & Messaging)
File: math-functions.md

type: languages title: "Beam ZetaSQL mathematical functions" <!-- Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. --> This page documents ZetaSQL scalar functions supported by Beam ZetaSQL. All mathematical functions return `NULL` if any of the input parameters is `NULL`. {{< table >}} | Operator syntax | Description | | - | - | | MOD(X, Y) | Returns the remainder of the division of X by Y | | CEIL(X) | Returns the smallest integral value (with FLOAT64 type) that is not less than X | | CEILING(X) | Synonym of CEIL(X) | | FLOOR(X) | Returns the largest integral value (with FLOAT64 type) that is not greater than X | {{< /table >}} ``` MOD(X, Y) ``` Description Modulo function: returns the remainder of the division of X by Y. Returned value has the same sign as X. ``` CEIL(X) ``` Description Returns the smallest integral value (with FLOAT64 type) that is not less than X. ``` CEILING(X) ``` Description Synonym of CEIL(X) ``` FLOOR(X) ``` Description Returns the largest integral value (with FLOAT64 type) that is not greater than X. Example behavior of Cloud Dataflow SQL rounding functions: {{< table >}} <table class="table-wrapper--equal-p"> <thead> <tr> <th>Input "X"</th> <th>CEIL(X)</th> <th>FLOOR(X)</th> </tr> </thead> <tbody> <tr> <td>2.0</td> <td>2.0</td> <td>2.0</td> </tr> <tr> <td>2.3</td> <td>3.0</td> <td>2.0</td> </tr> <tr> <td>2.8</td> <td>3.0</td> <td>2.0</td> </tr> <tr> <td>2.5</td> <td>3.0</td> <td>2.0</td> </tr> <tr> <td>-2.3</td> <td>-2.0</td> <td>-3.0</td> </tr> <tr> <td>-2.8</td> <td>-2.0</td> <td>-3.0</td> </tr> <tr> <td>-2.5</td> <td>-2.0</td> <td>-3.0</td> </tr> <tr> <td>0</td> <td>0</td> <td>0</td> </tr> </tbody> </table> {{< /table >}}
Project: Podman (App Definition and Development / Application Definition & Image Build)
File: MAINTAINERS.md

This page lists all active maintainers of this repository. If you were a maintainer and would like to add your name to the Emeritus list, please send us a PR. See for governance guidelines and how to become a maintainer. See for general contribution guidelines. , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC
Project: Shifu (Provisioning / Automation & Configuration)
File: CHANGELOG-v0.3.0.md

imeplement setup demo script by @MrLeea-13155bc in https://github.com/Edgenesis/shifu/pull/283 imeplement plc4x by @MrLeea-13155bc in https://github.com/Edgenesis/shifu/pull/275 customized data process (deviceshifu) for python by @seanli33056 in https://github.com/Edgenesis/shifu/pull/254 add push pipeline by @MrLeea-13155bc in https://github.com/Edgenesis/shifu/pull/296 <BugFix>Fix PLC4x pipeline by @MrLeea-13155bc in https://github.com/Edgenesis/shifu/pull/300 Fix usermetrics interval doc by @BtXin in https://github.com/Edgenesis/shifu/pull/301 <bugfix>fix dockerfile of plc4x by @MrLeea-13155bc in https://github.com/Edgenesis/shifu/pull/305 <bugfix>fix push pipeline and add plc4x deviceshifu into aio.sh by @MrLeea-13155bc in https://github.com/Edgenesis/shifu/pull/313 <bugfix>fix pipeline condition and add deviceshifu plc4x to aio by @MrLeea-13155bc in https://github.com/Edgenesis/shifu/pull/314 fix pipeline condition by @MrLeea-13155bc in https://github.com/Edgenesis/shifu/pull/318 cherry pick changelog v0.2.0 to main by @tomqin93 in https://github.com/Edgenesis/shifu/pull/286 add unit test for push telementry by @kris21he in https://github.com/Edgenesis/shifu/pull/280 Add unit test in deviceshifuhttp by @kris21he in https://github.com/Edgenesis/shifu/pull/291 update quay.io/brancz/kube-rbac-proxy to bitnami/kube-rbac-proxy by @tomqin93 in https://github.com/Edgenesis/shifu/pull/309 <enhance> Clear unused func and add a little UT by @MrLeea-13155bc in https://github.com/Edgenesis/shifu/pull/307 bump up version to Shifu v0.3.0-rc3 by @tomqin93 in https://github.com/Edgenesis/shifu/pull/316 remove incorrect milestones in README by @saiyan86 in https://github.com/Edgenesis/shifu/pull/287 Update README.md by @Yang-Xijie in https://github.com/Edgenesis/shifu/pull/282 Modified existing telemetry service design by @BtXin in https://github.com/Edgenesis/shifu/pull/279 Created guide for develop deviceshifu by @BtXin in https://github.com/Edgenesis/shifu/pull/295 Update develop-deviceshifu.md by @BtXin in https://github.com/Edgenesis/shifu/pull/297 fix typo by @Yang-Xijie in https://github.com/Edgenesis/shifu/pull/298 Full Changelog: https://github.com/Edgenesis/shifu/compare/v0.2.0...v0.3.0
Project: Shifu (Provisioning / Automation & Configuration)
File: CHANGELOG-v0.32.0.md

fix: typo by @testwill in fix:ci port conflict & merge pr#752 by @Kidr1cE in Bump go.uber.org/zap from 1.25.0 to 1.26.0 by @dependabot in Bump golang.org/x/crypto from 0.14.0 to 0.15.0 by @dependabot in Bump github.com/spf13/cobra from 1.7.0 to 1.8.0 by @dependabot in Bump golang.org/x/net from 0.17.0 to 0.18.0 by @dependabot in Bump github.com/onsi/ginkgo/v2 from 2.12.0 to 2.13.1 by @dependabot in Bump github.com/taosdata/driver-go/v3 from 3.5.0 to 3.5.1 by @dependabot in @testwill made their first contribution in Full Changelog: https://github.com/Edgenesis/shifu/compare/v0.31.0...v0.32.0
Project: Operator Framework (App Definition and Development / Application Definition & Image Build)
File: v1.34.0.md

title: v1.34.0 weight: 998966000 In the project `Makefile`, replace existing `docker-buildx` target with following definition. ```make docker-buildx: ## Build and push docker image for the manager for cross-platform support docker buildx create --name project-v3-builder docker buildx use project-v3-builder docker buildx build --push --platform=$(PLATFORMS) --tag ${IMG} -f Dockerfile . docker buildx rm project-v3-builder ``` See for more details.