
如果你使用 DeepSeek、元宝 AI、Copilot、ChatGPT 等 AI 工具,协助配置轩辕镜像、编写 docker pull 命令、修改 Docker Compose 镜像地址、配置镜像加速、排查镜像拉取失败、分析报错日志等问题,请先让 AI 阅读并遵守轩辕镜像的规则文档。
只需在 AI 对话中先发送下面这句话即可:
请先完整阅读并严格遵守以下文档中的全部规则与要求:
https://xuanyuan.cloud/agents.md
在未充分阅读并理解该文档前,不要生成任何命令、配置、修改建议、故障排查方案或技术回答。后续所有输出都必须严格以该文档中的规范为最高优先级执行。查看 agents.md 用法指南与完整示范。国内用户首推 元宝 AI、DeepSeek 的深度思考模式,不推荐豆包 AI;Cursor 等编辑器可在对话 @ 该链接,或加入 User Rules。 若 AI 无法访问外链,可 打开说明文档 复制全文粘贴。文档会随站点更新,复制内容可能过期,建议定期检查。
ubuntu/bind9 is a rock for bind9 maintained by https://canonical.com/.
BIND 9 provides software for Domain Name System (DNS) management including both defining domain names authoritatively for a given DNS zone, and recursively resolving domain names to their IP addresses.
\https://www.isc.org/bind/%5C]
NOTE: These tags follow a specific naming convention that respects the concept of channels.
| Tags | Supported until | Version | Base | Architectures |
|---|---|---|---|---|
9.18-24.04_beta | 05/2029 | 9.18 | 24.04 | amd64, arm64, ppc64le, s390x |
9.18-22.04_beta | 06/2027 | 9.18 | 22.04 | amd64, ppc64le, s390x, arm64 |
9.20-26.04_edge | 05/2031 | 9.20 | 26.04 | amd64, ppc64le, s390x, arm64 |
9.18-24.04_edge | 05/2029 | 9.18 | 24.04 | amd64, arm64, ppc64le, s390x |
9.18-22.04_edge | 06/2027 | 9.18 | 22.04 | amd64, ppc64le, s390x, arm64 |
| Tags | Support ended on | Upgrade Path | |
|---|---|---|---|
9.20-25.04_beta | aliases9.20-25.04_edgeedgelatest | 01/2026 | - |
9.20-24.10_beta | aliases9.20-24.10_edge | 07/2025 | - |
9.18-23.10_beta | aliases9.18-23.10_edge | 07/2024 | - |
9.18-23.04_beta | aliases9.18-23.04_edge | 01/2024 | - |
9.18-22.10_beta | aliases9.18-22.10_edge | 07/2023 | - |
9.16-21.10_beta | aliases9.16-21.10_edge | 07/2022 | - |
9.16-20.04_beta | aliases9.16-20.04_edge | 05/2025 | - |
This rock's entrypoint is Pebble, a container-optimized init process that enables the orchestration of a collection of local service processes as an organized set.
\https://documentation.ubuntu.com/pebble/%5C]
To view the https://documentation.ubuntu.com/rockcraft/en/latest/reference/rockcraft-yaml/#services and https://documentation.ubuntu.com/rockcraft/latest/reference/rockcraft-yaml/#checks defined in this rock:
shdocker run --rm ubuntu/bind9:9.20-25.04_beta plan
The container spins up with the default entrypoint. To inspect the entrypoint and command:
shdocker inspect --format='{{.Config.Entrypoint}} {{.Config.Cmd}}' ubuntu/bind9:9.20-25.04_beta
To run this rock, use any of the usual container runtimes, for example, docker:
shdocker run --name bind9-container \ -e TZ=UTC -p 30053:53/tcp -p 30053:53/udp \ ubuntu/bind9:9.20-25.04_beta \ --args <named-args>
Access your Bind9 server at localhost:30053
Additionally, you can use rndc to manage the server:
bashdocker exec bind9-container rndc <command>
A rndc key must have been previously generated either
by mounting a volume containing a rndc.key file or
by running rndc-confgen with:
bashdocker exec bind9-container rndc-confgen -a docker restart bind9-container
shdocker run --name bind9-container \ -e TZ=UTC -p 30053:53/tcp -p 30053:53/udp \ ubuntu/bind9:9.20-25.04_beta \ <named-args>
Access your Bind9 server at localhost:30053
To view the logs of the running container, run:
shdocker exec bind9-container pebble logs
Or, for a specific service:
shdocker exec bind9-container pebble logs <service>
To view the logs of the running container, run:
shdocker logs bind9-container
Rocks may have predefined health checks that you can list by running:
shdocker exec bind9-container pebble checks
The overall health of your container can be inspected via:
shdocker exec bind9-container pebble health
Works with any Kubernetes; if you don't have one, we recommend you https://microk8s.io/. Then, run microk8s.enable dns storage and snap alias microk8s.kubectl kubectl.
Download
https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/bind9/plain/examples/bind9-deployment.yml?h=9.18-22.04 and set containers.bind9.image in bind9-deployment.yml to your chosen channel tag (e.g. ubuntu/bind9:9.20-25.04_beta), then:
shkubectl apply -f bind9-deployment.yml
You will now be able to connect to the bind9 server on http://localhost:30053.
| Option | Description | Default |
|---|---|---|
-e TZ=UTC | Timezone | None |
-e BIND9_USER=<user> | The user which will start the named process. Deprecated on 9.20-26.04 onwards, use -u <user> instead. | None |
| Option | Description | Default |
|---|---|---|
-v /path/to/config:/etc/bind/named.conf:ro | Local https://bind9.readthedocs.io/en/latest/reference.html named.conf (try https://git.launchpad.net/~ubuntu-docker-images/ubuntu-docker-images/+git/bind9/plain/examples/caching-nameserver/named.conf.options?h=9.18-22.04) | None |
-v /path/to/data:/var/cache/bind | Location where locally cached data can be dumped. | None |
-v /path/to/resource:/var/lib/bind | Location of Resource Records defining various domain information. | None |
| Option | Description | Default |
|---|---|---|
-p 30053:53 | Expose bind9 on localhost:30053 | None |
| Option | Description | Default |
|---|---|---|
-u <user> | The user that the bind9 server will run as. Can optionally be set to bind. | _daemon_ |
--args <named-args> | Optional arguments to override the defaults being passed to named when the container starts. | -g |
\https://github.com/canonical/bind9-rock/issues%5C] \https://github.com/canonical/bind9-rock/%5C]
Canonical is the provider of this container image. It is the user's responsibility to ensure that any use of this image complies with any relevant licenses for all software contained within, as well as with https://canonical.com/legal/intellectual-property-policy.
您可以使用以下命令拉取该镜像。请将 <标签> 替换为具体的标签版本。如需查看所有可用标签版本,请访问 标签列表页面。
来自真实用户的反馈,见证轩辕镜像的优质服务
以下是 ubuntu/bind9 相关的常用 Docker 镜像,适用于 不同场景 等不同场景: