This is an automated email from the ASF dual-hosted git repository.
hello-stephen pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/doris-website.git
The following commit(s) were added to refs/heads/master by this push:
new d17e2de79a3 [doc](community) add the all-in-one image guide for
integration testing (#4078)
d17e2de79a3 is described below
commit d17e2de79a3bd8e3a08abc889101625d59f6efb7
Author: Mingyu Chen (Rayner) <[email protected]>
AuthorDate: Thu Aug 20 21:54:14 2026 +0800
[doc](community) add the all-in-one image guide for integration testing
(#4078)
## Summary
Adds a developer guide for the official `apache/doris:all-in-one-*`
image, under **Development & Debugging > Testing**.
The doc serves two purposes:
1. **For downstream / ecosystem projects** (connectors, SDKs, data
integration tools) that need a real Doris instance in their e2e / CI
runs rather than a mock: what the image provides as a test fixture, how
the `base` and `-full` tags differ, multi-architecture support, and
ready-to-copy usage with `docker run`, Docker Compose
(`service_healthy`) and GitHub Actions service containers, plus
configuration knobs, persistence and troubleshooting.
2. **For anyone building the image themselves**: a short section with
the three commands that cover the common cases, linking to the
[README](https://github.com/apache/doris/blob/master/docker/runtime/all-in-one/4.1/README.md)
in the Doris repository for everything else.
The build section is deliberately kept brief and the version number is
used only as an example, so a new Doris release does not require
maintaining this page.
Source of truth for the content: `docker/runtime/all-in-one/4.1/` in
apache/doris (added in apache/doris#66983).
## Changes
- `community/developer-guide/all-in-one-image.md` (EN)
-
`i18n/zh-CN/docusaurus-plugin-content-docs-community/current/developer-guide/all-in-one-image.md`
(ZH)
- `sidebarsCommunity.json`: new entry under **Testing**, after
`developer-guide/regression-testing`
## Verification
- `yarn docusaurus build` succeeds; both pages are generated for `en`
and `zh-CN`
- `yarn docs:links:changed`, `yarn docs:seo:changed`, `yarn
docs:i18n-sync:changed` and the frontmatter / markdown-structure lints
report no findings for the new files
- EN and ZH pages have identical heading structure, tables and code
blocks
- Ports, environment variables, config keys, mount paths and log paths
were checked against the Dockerfile, entrypoint.sh and conf files of the
image; the `all-in-one-4.1.3` and `-full` tags were confirmed to be
published as multi-arch (amd64 + arm64) on Docker Hub
---------
Co-authored-by: morningman <[email protected]>
Co-authored-by: Claude Opus 5 (1M context) <[email protected]>
---
community/developer-guide/all-in-one-image.md | 211 +++++++++++++++++++++
.../current/developer-guide/all-in-one-image.md | 210 ++++++++++++++++++++
sidebarsCommunity.json | 3 +-
3 files changed, 423 insertions(+), 1 deletion(-)
diff --git a/community/developer-guide/all-in-one-image.md
b/community/developer-guide/all-in-one-image.md
new file mode 100644
index 00000000000..aba60bebd25
--- /dev/null
+++ b/community/developer-guide/all-in-one-image.md
@@ -0,0 +1,211 @@
+---
+title: All-in-One Image for Integration Testing
+sidebar_label: All-in-One Image
+language: en
+description: The official Apache Doris all-in-one image runs one FE and one BE
in a single container, giving ecosystem projects a real Doris instance for e2e
and CI.
+keywords:
+ - Apache Doris
+ - all-in-one image
+ - integration testing
+ - e2e testing
+ - CI
+ - Docker
+ - Docker Compose
+ - GitHub Actions
+---
+
+<!--
+Licensed to the Apache Software Foundation (ASF) under one
+or more contributor license agreements. See the NOTICE file
+distributed with this work for additional information
+regarding copyright ownership. The ASF licenses this file
+to you 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.
+-->
+
+<!-- Knowledge Type: Tool Usage -->
+<!-- Applicable Scenarios: Ecosystem project integration testing / CI
environment setup -->
+
+Ecosystem projects around Apache Doris — connectors, SDKs, data integration
tools — usually need a real Doris instance in their e2e / CI runs rather than a
mock. The official all-in-one image is built for exactly that: one FE and one
BE in a single container, ready to use on startup, with a health check, so it
can be dropped in as a test fixture.
+
+This document describes what the image provides, how to use it, and how to
build it yourself.
+
+:::caution Note
+
+This image is a test fixture designed for integration testing: a single FE and
a single BE, one replica, memory settings tuned down for CI runners, and no
data persistence by default. Do not use it for production deployment.
+
+:::
+
+## Image overview
+
+Image tags look like `apache/doris:all-in-one-<version>`, for example
`apache/doris:all-in-one-4.1.3`. Every example below uses 4.1.3 — replace it
with the version you need. For the available tags, see the [apache/doris
repository on Docker
Hub](https://hub.docker.com/r/apache/doris/tags?name=all-in-one).
+
+The image is assembled from the official `apache/doris:fe-<version>` and
`apache/doris:be-<version>` images, so what runs inside it is the released
artifact itself. Only two things are done for the CI use case: debug info is
stripped from `doris_be` (`.symtab` is kept, so crash backtraces still resolve
function names), and the JNI scanner directories the tag does not need are
removed.
+
+The behaviors that matter for integration testing:
+
+| Feature | Description |
+| --- | --- |
+| Ready to use | FE startup, `ALTER SYSTEM ADD BACKEND` registration of the
BE, and waiting for the BE to come online all happen inside the container. No
external script is involved |
+| Health check | The image ships a `HEALTHCHECK` that turns `healthy` only
once FE is ready and the BE is online, usually within 20 seconds. CI can wait
on that status instead of calling `sleep` |
+| Single replica | `force_olap_table_replication_num = 1` is set, so `CREATE
TABLE` does not need `replication_num` |
+| Bounded resources | Memory is tuned down for CI runners: FE heap
`-Xmx2048m`, the BE-side JNI heap `-Xmx1024m`, and BE `mem_limit = 40%` |
+| Fail-fast | If either FE or BE exits, the container exits non-zero right
away instead of restarting silently, so a failure surfaces immediately in CI |
+| Graceful shutdown | `docker stop` stops BE first, then FE, and exits 0 |
+| Multi-architecture | One tag covers both linux/amd64 and linux/arm64 |
+
+### The two tags: base and -full
+
+| Tag | Covers | Image size (4.1.3, uncompressed) |
+| --- | --- | --- |
+| `apache/doris:all-in-one-<version>` | Internal tables, Hive, Iceberg
(including system tables), Paimon, JDBC catalogs, external table writeback,
Java UDF | About 2.5 GB |
+| `apache/doris:all-in-one-<version>-full` | Everything above, plus Hudi,
Trino connector, MaxCompute | About 3.0 GB |
+
+The sizes were measured on 4.1.3. For reference, the same payload without
stripping and pruning is about 4.9 GB.
+
+**Only pick `-full` if the tests actually read Hudi tables, go through the
Trino connector, or use MaxCompute.** Otherwise use the tag without the suffix.
+
+The difference between the two tags comes from how BE loads its scanners: at
startup BE enumerates the directories under `be/lib/java_extensions/` to load
JNI scanners. There is no list and no configuration key, so a tag supports
exactly the formats whose directory it ships. Note that Hive and Iceberg
**data** reads go through BE's native parquet / orc reader rather than these
JNI scanners, so both tags support them.
+
+### Multi-architecture support
+
+`apache/doris:all-in-one-4.1.3` is an OCI image index carrying one manifest
for linux/amd64 and one for linux/arm64. A `docker pull` picks the one matching
the host automatically, the same way `apache/doris:fe-4.1.3` does, so CI does
not need different tags for runners of different architectures.
+
+```shell
+docker buildx imagetools inspect apache/doris:all-in-one-4.1.3
+```
+
+:::caution Note
+
+A Doris BE generally cannot run under cross-architecture emulation. Starting
the amd64 image with `--platform linux/amd64` on Apple Silicon, for instance,
segfaults, and the official `apache/doris:be-*` images behave the same way. Run
the image on real hardware of the matching architecture.
+
+:::
+
+## Using it in integration tests
+
+### Connection information
+
+| Item | Description |
+| --- | --- |
+| MySQL protocol | Port `9030`, user `root`, no password |
+| FE HTTP | Port `8030`, `/api/health` needs no authentication |
+| BE HTTP | Port `8040`, the stream load endpoint |
+| BE heartbeat | Port `9050`, used inside the container, normally not mapped
to the host |
+
+### Plain docker run
+
+```shell
+docker run -d --name doris \
+ -p 9030:9030 -p 8030:8030 -p 8040:8040 \
+ apache/doris:all-in-one-4.1.3
+
+# Wait until the container is healthy
+until [ "$(docker inspect -f '{{.State.Health.Status}}' doris)" = healthy ];
do sleep 1; done
+
+mysql -uroot -h127.0.0.1 -P9030 -e "SHOW BACKENDS"
+```
+
+The image ships a MySQL client, so if the host does not have one, run it
inside the container instead:
+
+```shell
+docker exec doris mysql -uroot -h127.0.0.1 -P9030 -e "SHOW BACKENDS"
+```
+
+### Docker Compose
+
+With `depends_on` and `service_healthy`, the test container starts only after
Doris is genuinely usable:
+
+```yaml
+services:
+ doris:
+ image: apache/doris:all-in-one-4.1.3
+ ports: ["9030:9030", "8030:8030", "8040:8040"]
+
+ integration-test:
+ image: my-project-tests:latest
+ depends_on:
+ doris:
+ condition: service_healthy
+```
+
+### GitHub Actions
+
+As a service container, GitHub Actions waits for the container to become
`healthy` before running the `steps`, so the test code does not need its own
retry-and-wait logic:
+
+```yaml
+jobs:
+ e2e:
+ runs-on: ubuntu-latest
+ services:
+ doris:
+ image: apache/doris:all-in-one-4.1.3
+ ports: ['9030:9030', '8030:8030', '8040:8040']
+ steps:
+ - uses: actions/checkout@v4
+ - run: mvn -B verify -Pe2e
+```
+
+### Adjusting the configuration
+
+The image already carries a set of integration-test defaults. To change
something, use the two environment variables below to append configuration
items; they are appended to the end of `fe.conf` and `be.conf` respectively at
startup, and the last assignment wins:
+
+```shell
+docker run -d --name doris \
+ -p 9030:9030 -p 8030:8030 -p 8040:8040 \
+ -e BE_CONFIG_EXTRA="mem_limit = 80%" \
+ -e FE_CONFIG_EXTRA="qe_max_connection = 2048" \
+ apache/doris:all-in-one-4.1.3
+```
+
+| Environment variable | Effect |
+| --- | --- |
+| `FE_CONFIG_EXTRA` | Appended to `fe.conf`. Separate multiple items with
newlines |
+| `BE_CONFIG_EXTRA` | Appended to `be.conf`. Separate multiple items with
newlines |
+
+**Data persistence**: there is none by default, so the data is gone once the
container is removed, which is usually what CI wants. To keep the data, mount
`/opt/apache-doris/fe/doris-meta` and `/opt/apache-doris/be/storage`. The
startup path is idempotent, so the same data directory can be started again and
again.
+
+### Troubleshooting
+
+- `docker logs <container>` carries the entrypoint's startup log and FE's
console stream, which tells you where the cluster is stuck during startup.
+- The full logs live inside the container at `fe/log/fe.log` and
`be/log/be.INFO`.
+- A non-zero container exit means FE or BE died. The log right before the exit
names which one it was and which log file to read.
+- Tests handling larger volumes of data may need `vm.max_map_count` raised
**on the host** (`sysctl -w vm.max_map_count=2000000`). It is not a namespaced
sysctl, so the container cannot set it, which is why the image skips
`start_be.sh`'s check for it.
+
+## Building the image yourself
+
+The Dockerfile and the build script live under
`docker/runtime/all-in-one/<release-line>/` in the main Doris repository, where
`4.1` is currently available. Release lines differ enough in artifact layout
that each gets its own directory instead of a version switch inside a single
Dockerfile.
+
+`build.sh` is the only entry point. The build context is always the repository
root, and the script itself can be run from any directory:
+
+```shell
+# Build both the base and the -full tag from the official 4.1.3 component
images
+# (host architecture only)
+./build.sh -v 4.1.3
+
+# Build base only, then run a smoke test against it
+./build.sh -v 4.1.3 -f base -t
+
+# Build from a local ./output, which is handy for verifying your own changes
+# Requires a completed Doris build producing ./output/fe and ./output/be
+./build.sh -v dev -s local
+```
+
+Without `--platform`, only the host architecture is built. Multi-architecture
builds need it spelled out, for example `./build.sh -v 4.1.3 --platform
linux/amd64,linux/arm64 --push`. Since a cross-architecture build goes through
emulation and takes a long time, building each architecture natively on its own
machine and then joining the results with `docker buildx imagetools create` is
the better choice for a release.
+
+`./build.sh --help` lists the remaining options.
+
+:::tip
+
+For implementation details — what the image prunes, why some directories that
look like external table extras must not be pruned, where the size goes, and
how to run the smoke test — see the
[README](https://github.com/apache/doris/blob/master/docker/runtime/all-in-one/4.1/README.md)
in that directory.
+
+:::
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/developer-guide/all-in-one-image.md
b/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/developer-guide/all-in-one-image.md
new file mode 100644
index 00000000000..571230ae64e
--- /dev/null
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/developer-guide/all-in-one-image.md
@@ -0,0 +1,210 @@
+---
+title: 集成测试用 all-in-one 镜像
+sidebar_label: All-in-One 镜像
+language: zh-CN
+description: 介绍 Apache Doris 官方 all-in-one 容器镜像，它在单个容器中运行一套 FE + BE，可供上下游生态项目在
e2e / CI 中作为真实 Doris 环境使用，并说明镜像能力、base 与 -full 标签的差异、多架构支持以及自行构建方式。
+keywords:
+ - Apache Doris
+ - all-in-one 镜像
+ - 集成测试
+ - e2e 测试
+ - CI
+ - Docker
+ - Docker Compose
+ - GitHub Actions
+---
+
+<!--
+Licensed to the Apache Software Foundation (ASF) under one
+or more contributor license agreements. See the NOTICE file
+distributed with this work for additional information
+regarding copyright ownership. The ASF licenses this file
+to you 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.
+-->
+
+<!-- 知识类型: 工具使用 -->
+<!-- 适用场景: 生态项目集成测试 / CI 环境搭建 -->
+
+Connector、SDK、数据集成工具等 Apache Doris 上下游项目，在 e2e / CI 中往往需要一个真实的 Doris 实例，而不是
Mock。为此 Doris 官方提供了 all-in-one 镜像：单个容器内跑一套 FE + BE，启动即可用，带健康检查，可以直接当作测试夹具（test
fixture）使用。
+
+本文介绍这个镜像的能力和用法，以及如何自行构建它。
+
+:::caution 注意
+
+这个镜像是为集成测试设计的测试夹具：单 FE 单 BE、单副本、内存参数按 CI runner 调小、默认不持久化数据。请勿用于生产部署。
+
+:::
+
+## 镜像概览
+
+镜像标签形如 `apache/doris:all-in-one-<version>`，例如
`apache/doris:all-in-one-4.1.3`。本文所有示例都以 4.1.3 为例，换成你需要的版本即可；可用标签见 [Docker Hub
上的 apache/doris 仓库](https://hub.docker.com/r/apache/doris/tags?name=all-in-one)。
+
+镜像由官方的 `apache/doris:fe-<version>` 和 `apache/doris:be-<version>`
组装而成，里面跑的就是正式发布的产物本身，只针对 CI 场景做了两处处理：对 `doris_be` 剥离调试信息（保留
`.symtab`，崩溃堆栈仍能解析出函数名），以及裁掉当前标签用不到的 JNI scanner 目录。
+
+面向集成测试的几个关键行为：
+
+| 特性 | 说明 |
+| --- | --- |
+| 开箱即用 | 容器内部已完成 FE 启动、`ALTER SYSTEM ADD BACKEND` 注册 BE、等待 BE 上线的全过程，不需要外部脚本介入
|
+| 健康检查 | 镜像自带 `HEALTHCHECK`，只有 FE 就绪且 BE 已上线时才会变为 `healthy`，通常在 20 秒内完成。CI
里直接等这个状态即可，不需要 `sleep` |
+| 单副本 | 已设置 `force_olap_table_replication_num = 1`，`CREATE TABLE` 不必再写
`replication_num` |
+| 资源可控 | 按 CI runner 的规格调小了内存：FE 堆 `-Xmx2048m`，BE 侧 JNI 堆 `-Xmx1024m`，BE
`mem_limit = 40%` |
+| fail-fast | FE 或 BE 任一进程退出，容器随即以非零状态退出，不会静默重启，故障会立刻在 CI 中暴露出来 |
+| 优雅停止 | `docker stop` 会先停 BE 再停 FE，正常退出 0 |
+| 多架构 | 同一个标签同时覆盖 linux/amd64 和 linux/arm64 |
+
+### 两个标签：base 与 -full
+
+| 标签 | 覆盖能力 | 镜像体积（4.1.3，未压缩） |
+| --- | --- | --- |
+| `apache/doris:all-in-one-<version>` | 内表、Hive、Iceberg（含系统表）、Paimon、JDBC
Catalog、外表写回、Java UDF | 约 2.5 GB |
+| `apache/doris:all-in-one-<version>-full` | 在上述基础上增加 Hudi、Trino
Connector、MaxCompute | 约 3.0 GB |
+
+体积是在 4.1.3 上实测的，作为参照，未经剥离和裁剪的等价负载约为 4.9 GB。
+
+**只有测试确实要读 Hudi 表、走 Trino Connector 或 MaxCompute 时才需要 `-full`**，其余场景用不带后缀的标签即可。
+
+两个标签的差异来自 BE 的加载方式：BE 启动时通过枚举 `be/lib/java_extensions/` 下的目录来加载 JNI
scanner，既没有列表也没有配置项，因此镜像里保留了哪些目录，就支持哪些格式。需要注意的是，Hive 和 Iceberg 的**数据**读取走的是 BE
原生的 parquet / orc reader，不属于这套 JNI scanner，因此两个标签都支持。
+
+### 多架构支持
+
+`apache/doris:all-in-one-4.1.3` 是一个 OCI image index，下面挂着 linux/amd64 和
linux/arm64 两个 manifest，`docker pull` 会自动选择与宿主机匹配的那一个，行为与
`apache/doris:fe-4.1.3` 一致。CI 中不需要为不同架构的 runner 写不同的标签。
+
+```shell
+docker buildx imagetools inspect apache/doris:all-in-one-4.1.3
+```
+
+:::caution 注意
+
+Doris BE 通常无法在跨架构模拟下运行。例如在 Apple Silicon 上用 `--platform linux/amd64` 拉起 amd64
镜像会 segfault，官方的 `apache/doris:be-*` 镜像同样如此。请在与镜像架构一致的真实硬件上运行。
+
+:::
+
+## 在集成测试中使用
+
+### 连接信息
+
+| 项 | 说明 |
+| --- | --- |
+| MySQL 协议 | 端口 `9030`，用户 `root`，无密码 |
+| FE HTTP | 端口 `8030`，`/api/health` 无需鉴权 |
+| BE HTTP | 端口 `8040`，Stream Load 入口 |
+| BE 心跳 | 端口 `9050`，容器内部使用，一般不需要映射到宿主机 |
+
+### 直接用 docker run
+
+```shell
+docker run -d --name doris \
+ -p 9030:9030 -p 8030:8030 -p 8040:8040 \
+ apache/doris:all-in-one-4.1.3
+
+# 等待容器变为 healthy
+until [ "$(docker inspect -f '{{.State.Health.Status}}' doris)" = healthy ];
do sleep 1; done
+
+mysql -uroot -h127.0.0.1 -P9030 -e "SHOW BACKENDS"
+```
+
+镜像内自带 MySQL 客户端，宿主机上没有装的话，可以直接在容器里执行：
+
+```shell
+docker exec doris mysql -uroot -h127.0.0.1 -P9030 -e "SHOW BACKENDS"
+```
+
+### Docker Compose
+
+`depends_on` 配合 `service_healthy`，测试容器会在 Doris 真正可用之后才启动：
+
+```yaml
+services:
+ doris:
+ image: apache/doris:all-in-one-4.1.3
+ ports: ["9030:9030", "8030:8030", "8040:8040"]
+
+ integration-test:
+ image: my-project-tests:latest
+ depends_on:
+ doris:
+ condition: service_healthy
+```
+
+### GitHub Actions
+
+作为 service container 使用时，GitHub Actions 会自动等待容器 `healthy` 之后才执行
`steps`，测试代码里不需要再写重试等待逻辑：
+
+```yaml
+jobs:
+ e2e:
+ runs-on: ubuntu-latest
+ services:
+ doris:
+ image: apache/doris:all-in-one-4.1.3
+ ports: ['9030:9030', '8030:8030', '8040:8040']
+ steps:
+ - uses: actions/checkout@v4
+ - run: mvn -B verify -Pe2e
+```
+
+### 调整配置
+
+镜像里已经是一套面向集成测试的默认配置。需要改动时，用下面两个环境变量追加配置项，它们会在启动时分别附加到 `fe.conf` 和 `be.conf`
的末尾（后写的赋值生效）：
+
+```shell
+docker run -d --name doris \
+ -p 9030:9030 -p 8030:8030 -p 8040:8040 \
+ -e BE_CONFIG_EXTRA="mem_limit = 80%" \
+ -e FE_CONFIG_EXTRA="qe_max_connection = 2048" \
+ apache/doris:all-in-one-4.1.3
+```
+
+| 环境变量 | 作用 |
+| --- | --- |
+| `FE_CONFIG_EXTRA` | 追加到 `fe.conf`，多行配置用换行分隔 |
+| `BE_CONFIG_EXTRA` | 追加到 `be.conf`，多行配置用换行分隔 |
+
+**数据持久化**：默认不持久化，容器销毁后数据即消失，这通常正是 CI 想要的。需要保留数据时，挂载
`/opt/apache-doris/fe/doris-meta` 和 `/opt/apache-doris/be/storage`
即可，启动流程是幂等的，同一份数据目录可以反复拉起。
+
+### 排查问题
+
+- `docker logs <container>` 输出的是 entrypoint 的启动日志和 FE 的 console
流，可用于判断集群卡在启动的哪一步。
+- 完整日志在容器内的 `fe/log/fe.log` 和 `be/log/be.INFO`。
+- 容器非零退出，说明 FE 或 BE 挂了，退出前的日志里会指明是哪一个以及去看哪个日志文件。
+- 数据量较大的测试可能需要在**宿主机**上调大 `vm.max_map_count`（`sysctl -w
vm.max_map_count=2000000`）。这不是 namespace 化的 sysctl，容器内改不了，因此镜像里跳过了
`start_be.sh` 对它的检查。
+
+## 自行构建镜像
+
+Dockerfile 和构建脚本位于 Doris 主仓库的 `docker/runtime/all-in-one/<版本线>/` 下，目前提供
`4.1`。各版本线的产物布局差异较大，因此按版本线分目录，而不是在一份 Dockerfile 里做版本开关。
+
+`build.sh` 是唯一的入口，构建上下文固定为仓库根目录，脚本本身可以在任意目录下执行：
+
+```shell
+# 用官方 4.1.3 组件镜像构建 base 和 -full 两个标签（仅宿主机架构）
+./build.sh -v 4.1.3
+
+# 只构建 base，并跑一遍冒烟测试
+./build.sh -v 4.1.3 -f base -t
+
+# 用本地编译产物 ./output 构建，便于验证自己修改过的内核
+# 需先完成 Doris 编译，产出 ./output/fe 和 ./output/be
+./build.sh -v dev -s local
+```
+
+不带 `--platform` 时只构建宿主机架构。多架构需要显式指定，例如 `./build.sh -v 4.1.3 --platform
linux/amd64,linux/arm64 --push`。跨架构构建走模拟，耗时很长，因此发布时更推荐在各架构的机器上分别构建，再用 `docker
buildx imagetools create` 合并成一个标签。
+
+`./build.sh --help` 列出全部选项。
+
+:::tip
+
+镜像裁剪了哪些内容、为什么有些看起来像外表插件的目录其实不能裁、体积构成、冒烟测试怎么跑等实现细节，见目录下的
[README](https://github.com/apache/doris/blob/master/docker/runtime/all-in-one/4.1/README.md)。
+
+:::
diff --git a/sidebarsCommunity.json b/sidebarsCommunity.json
index 67cfc62837c..e99903f2360 100644
--- a/sidebarsCommunity.json
+++ b/sidebarsCommunity.json
@@ -82,7 +82,8 @@
"type": "category",
"label": "Testing",
"items": [
- "developer-guide/regression-testing"
+ "developer-guide/regression-testing",
+ "developer-guide/all-in-one-image"
]
},
{
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
