
如果你使用 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 无法访问外链,可 打开说明文档 复制全文粘贴。文档会随站点更新,复制内容可能过期,建议定期检查。
nightly-jdk15-buster 36a4b59-jdk15-buster nightly-jdk-buster 36a4b59-jdk-buster nightly-buster 36a4b59-busternightly-jdk15-slim-buster 36a4b59-jdk15-slim-buster nightly-jdk-slim-buster 36a4b59-jdk-slim-buster nightly-slim-buster 36a4b59-slim-busternightly-jdk11-buster 36a4b59-jdk11-busternightly-jdk11-slim-buster 36a4b59-jdk11-slim-busternightly-jdk8-buster 36a4b59-jdk8-busternightly-jdk8-slim-buster 36a4b59-jdk8-slim-buster1.8.0-jdk15-buster 1-jdk15-buster 1.8-jdk15-buster jdk15-buster 1.8.0-jdk-buster 1-jdk-buster 1.8-jdk-buster jdk-buster 1.8.0-buster 1-buster 1.8-buster buster1.8.0-jdk15-slim-buster 1-jdk15-slim-buster 1.8-jdk15-slim-buster jdk15-slim-buster 1.8.0-jdk-slim-buster 1-jdk-slim-buster 1.8-jdk-slim-buster jdk-slim-buster 1.8.0-slim-buster 1-slim-buster 1.8-slim-buster slim-buster1.8.0-jdk11-buster 1-jdk11-buster 1.8-jdk11-buster jdk11-buster1.8.0-jdk11-slim-buster 1-jdk11-slim-buster 1.8-jdk11-slim-buster jdk11-slim-buster1.8.0-jdk8-buster 1-jdk8-buster 1.8-jdk8-buster jdk8-buster1.8.0-jdk8-slim-buster 1-jdk8-slim-buster 1.8-jdk8-slim-buster jdk8-slim-buster1.8.0-jdk15-windowsservercore-1809 1-jdk15-windowsservercore-1809 1.8-jdk15-windowsservercore-1809 jdk15-windowsservercore-1809 1.8.0-jdk-windowsservercore-1809 1-jdk-windowsservercore-1809 1.8-jdk-windowsservercore-1809 jdk-windowsservercore-1809 1.8.0-windowsservercore-1809 1-windowsservercore-1809 1.8-windowsservercore-1809 windowsservercore-18091.8.0-jdk11-windowsservercore-1809 1-jdk11-windowsservercore-1809 1.8-jdk11-windowsservercore-1809 jdk11-windowsservercore-18091.8.0-jdk8-windowsservercore-1809 1-jdk8-windowsservercore-1809 1.8-jdk8-windowsservercore-1809 jdk8-windowsservercore-18091.8.0-jdk15-windowsservercore-ltsc2016 1-jdk15-windowsservercore-ltsc2016 1.8-jdk15-windowsservercore-ltsc2016 jdk15-windowsservercore-ltsc2016 1.8.0-jdk-windowsservercore-ltsc2016 1-jdk-windowsservercore-ltsc2016 1.8-jdk-windowsservercore-ltsc2016 jdk-windowsservercore-ltsc2016 1.8.0-windowsservercore-ltsc2016 1-windowsservercore-ltsc2016 1.8-windowsservercore-ltsc2016 windowsservercore-ltsc20161.8.0-jdk11-windowsservercore-ltsc2016 1-jdk11-windowsservercore-ltsc2016 1.8-jdk11-windowsservercore-ltsc2016 jdk11-windowsservercore-ltsc20161.8.0-jdk8-windowsservercore-ltsc2016 1-jdk8-windowsservercore-ltsc2016 1.8-jdk8-windowsservercore-ltsc2016 jdk8-windowsservercore-ltsc20161.7.1-jdk15-buster 1.7-jdk15-buster 1.7.1-jdk-buster 1.7-jdk-buster 1.7.1-buster 1.7-buster1.7.1-jdk15-slim-buster 1.7-jdk15-slim-buster 1.7.1-jdk-slim-buster 1.7-jdk-slim-buster 1.7.1-slim-buster 1.7-slim-buster1.7.1-jdk11-buster 1.7-jdk11-buster1.7.1-jdk11-slim-buster 1.7-jdk11-slim-buster1.7.1-jdk8-buster 1.7-jdk8-buster1.7.1-jdk8-slim-buster 1.7-jdk8-slim-buster1.7.1-jdk15-windowsservercore-1809 1.7-jdk15-windowsservercore-1809 1.7.1-jdk-windowsservercore-1809 1.7-jdk-windowsservercore-1809 1.7.1-windowsservercore-1809 1.7-windowsservercore-18091.7.1-jdk11-windowsservercore-1809 1.7-jdk11-windowsservercore-18091.7.1-jdk8-windowsservercore-1809 1.7-jdk8-windowsservercore-18091.7.1-jdk15-windowsservercore-ltsc2016 1.7-jdk15-windowsservercore-ltsc2016 1.7.1-jdk-windowsservercore-ltsc2016 1.7-jdk-windowsservercore-ltsc2016 1.7.1-windowsservercore-ltsc2016 1.7-windowsservercore-ltsc20161.7.1-jdk11-windowsservercore-ltsc2016 1.7-jdk11-windowsservercore-ltsc20161.7.1-jdk8-windowsservercore-ltsc2016 1.7-jdk8-windowsservercore-ltsc20161.7-jdk, 1.7.1-jdk, 1.7-jdk15, 1.7, 1.7.1-jdk15, 1.7.1
1.7.1-jdk15-buster1.7.1-jdk15-windowsservercore-18091.7.1-jdk15-windowsservercore-ltsc20161.7.1-jdk8, 1.7-jdk8
1.7.1-jdk8-buster1.7.1-jdk8-windowsservercore-18091.7.1-jdk8-windowsservercore-ltsc2016jdk11-slim, 1-jdk11-slim, 1.8.0-jdk11-slim, 1.8-jdk11-slim
1.8.0-jdk11-slim-buster1.7-jdk15-slim, 1.7.1-jdk-slim, 1.7-jdk-slim, 1.7.1-jdk15-slim, 1.7.1-slim, 1.7-slim
1.7.1-jdk15-slim-busterjdk-windowsservercore, windowsservercore, 1.8.0-jdk-windowsservercore, 1.8-jdk-windowsservercore, 1-windowsservercore, 1.8.0-jdk15-windowsservercore, 1.8.0-windowsservercore, 1-jdk15-windowsservercore, jdk15-windowsservercore, 1.8-windowsservercore, 1-jdk-windowsservercore, 1.8-jdk15-windowsservercore
1.8.0-jdk15-windowsservercore-18091.8.0-jdk15-windowsservercore-ltsc20161.7.1-jdk15-windowsservercore, 1.7-jdk15-windowsservercore, 1.7.1-windowsservercore, 1.7.1-jdk-windowsservercore, 1.7-jdk-windowsservercore, 1.7-windowsservercore
1.7.1-jdk15-windowsservercore-18091.7.1-jdk15-windowsservercore-ltsc2016jdk15-slim, 1-slim, 1.8.0-jdk15-slim, 1.8-jdk-slim, 1-jdk-slim, 1.8.0-slim, 1-jdk15-slim, jdk-slim, 1.8-jdk15-slim, 1.8-slim, slim, 1.8.0-jdk-slim
1.8.0-jdk15-slim-busterjdk11-windowsservercore, 1.8-jdk11-windowsservercore, 1.8.0-jdk11-windowsservercore, 1-jdk11-windowsservercore
1.8.0-jdk11-windowsservercore-18091.8.0-jdk11-windowsservercore-ltsc2016latest, jdk15, 1, 1.8.0-jdk15, 1-jdk, 1.8, 1.8-jdk, 1.8.0, 1-jdk15, 1.8.0-jdk, jdk, 1.8-jdk15
1.8.0-jdk15-buster1.8.0-jdk15-windowsservercore-18091.8.0-jdk15-windowsservercore-ltsc201636a4b59-jdk11-slim, nightly-jdk11-slim
nightly-jdk11-slim-busterjdk11, 1.8.0-jdk11, 1-jdk11, 1.8-jdk11
1.8.0-jdk11-buster1.8.0-jdk11-windowsservercore-18091.8.0-jdk11-windowsservercore-ltsc20161-jdk8-slim, 1.8-jdk8-slim, jdk8-slim, 1.8.0-jdk8-slim
1.8.0-jdk8-slim-buster36a4b59-jdk, nightly, nightly-jdk, 36a4b59-jdk15, 36a4b59, nightly-jdk15
nightly-jdk15-buster1.7-jdk8-windowsservercore, 1.7.1-jdk8-windowsservercore
1.7.1-jdk8-windowsservercore-18091.7.1-jdk8-windowsservercore-ltsc201636a4b59-jdk15-slim, 36a4b59-jdk-slim, nightly-slim, nightly-jdk15-slim, nightly-jdk-slim, 36a4b59-slim
nightly-jdk15-slim-buster1-jdk8, jdk8, 1.8-jdk8, 1.8.0-jdk8
1.8.0-jdk8-buster1.8.0-jdk8-windowsservercore-18091.8.0-jdk8-windowsservercore-ltsc20161.7-jdk11, 1.7.1-jdk11
1.7.1-jdk11-buster1.7.1-jdk11-windowsservercore-18091.7.1-jdk11-windowsservercore-ltsc2016jdk8-windowsservercore, 1.8-jdk8-windowsservercore, 1-jdk8-windowsservercore, 1.8.0-jdk8-windowsservercore
1.8.0-jdk8-windowsservercore-18091.8.0-jdk8-windowsservercore-ltsc20161.7.1-jdk11-slim, 1.7-jdk11-slim
1.7.1-jdk11-slim-busternightly-jdk8, 36a4b59-jdk8
nightly-jdk8-buster1.7-jdk8-slim, 1.7.1-jdk8-slim
1.7.1-jdk8-slim-buster1.7.1-jdk11-windowsservercore, 1.7-jdk11-windowsservercore
1.7.1-jdk11-windowsservercore-18091.7.1-jdk11-windowsservercore-ltsc201636a4b59-jdk11, nightly-jdk11
nightly-jdk11-busternightly-jdk8-slim, 36a4b59-jdk8-slim
nightly-jdk8-slim-busterlinux/amd64, linux/arm64/v8, windows/amd64来自 ABCL主页:
Armed Bear Common Lisp (ABCL) 是Common Lisp语言的完整实现,包含解释器和编译器,运行在JVM上。最初是为J编辑器设计的脚本语言,现在支持JSR-223(Java脚本API):它可以作为任何Java应用中的脚本引擎。此外,它还可以通过Java与Lisp集成API来实现应用的(部分)功能。
dockerfileFROM docker.xuanyuan.run/daewok/abcl:latest COPY . /usr/src/app WORKDIR /usr/src/app CMD [ "abcl", "--load", "./your-daemon-or-script.lisp" ]
然后构建并运行Docker镜像:
console$ docker build -t my-abcl-app $ docker run -it --rm --name my-running-app my-abcl-app
对于许多简单的单文件项目,编写完整的Dockerfile可能不太方便。这种情况下,可以直接使用ABCL Docker镜像运行Lisp脚本:
console$ docker run -it --rm --name my-running-script -v "$PWD":/usr/src/app -w /usr/src/app daewok/abcl:latest abcl --load ./your-daemon-or-script.lisp
SLIME 为Common Lisp开发提供了便捷有趣的环境。要使用SLIME开发,首先在容器中启动Swank服务器:
console$ docker run -it --rm --name abcl-slime -p 127.0.0.1:4005:4005 -v /path/to/slime:/usr/src/slime -v "$PWD":/usr/src/app -w /usr/src/app daewok/abcl:latest abcl --load /usr/src/slime/swank-loader.lisp --eval '(swank-loader:init)' --eval '(swank:create-server :dont-close t :interface "0.0.0.0")'
然后,在已加载SLIME的Emacs中,输入:
emacsM-x slime-connect RET RET RET
该镜像提供多种变体,适用于不同使用场景:
daewok/abcl:<version>这是默认镜像。如果不确定需求,建议使用此版本。它既可以作为临时容器(挂载源代码并启动以运行应用),也可以作为构建其他镜像的基础。部分标签包含buster或stretch等名称,这些是Debian发行版的代号,指示镜像基于哪个版本。如果需要安装额外包,建议显式指定这些标签以减少Debian版本更新带来的问题。此镜像包含quicklisp安装程序(位于/usr/local/share/common-lisp/source/quicklisp/quicklisp.lisp),以及/usr/local/bin/install-quicklisp脚本用于安装Quicklisp。可通过以下环境变量配置Quicklisp安装:
QUICKLISP_DIST_VERSION: 要使用的发行版版本(格式为yyyy-mm-dd),latest表示安装最新版本(默认)。QUICKLISP_CLIENT_VERSION: 客户端版本(格式为yyyy-mm-dd),latest表示最新版本(默认)。QUICKLISP_ADD_TO_INIT_FILE: 如果设置为true,则使用(ql:add-to-init-file)将加载Quicklisp的代码添加到用户初始化文件中,默认未设置。此外,镜像包含cl-launch,提供统一接口运行Lisp实现。daewok/abcl:<version>-slim此镜像不包含默认标签中的常用包,仅包含运行ABCL所需的最小包。除非在空间受限且仅部署此镜像的环境中,否则强烈建议使用默认镜像。
daewok/abcl:<version>-windowsservercore此镜像基于https://hub.docker.com/_/microsoft-windows-servercore%EF%BC%8C%E4%BB%85%E5%9C%A8%E6%94%AF%E6%8C%81%E8%AF%A5%E9%95%9C%E5%83%8F%E7%9A%84%E7%8E%AF%E5%A2%83%E4%B8%AD%E5%B7%A5%E4%BD%9C%EF%BC%88%E5%A6%82Windows 10专业版/企业版(周年更新)或Windows Server 2016)。有关如何在Windows上运行Docker的信息,请参考Microsoft提供的快速入门指南:
ABCL使用 https://www.gnu.org/copyleft/gpl.html 许可证,并带有 https://www.gnu.org/software/classpath/license.html%E3%80%82%E6%9E%84%E5%BB%BA%E9%95%9C%E5%83%8F%E7%9A%84Dockerfile%E4%BD%BF%E7%94%A8BSD-2-Clause%E8%AE%B8%E5%8F%AF%E8%AF%81%E3%80%82%E4%B8%8E%E6%89%80%E6%9C%89Docker%E9%95%9C%E5%83%8F%E4%B8%80%E6%A0%B7%EF%BC%8C%E5%85%B6%E4%B8%AD%E5%8F%AF%E8%83%BD%E5%8C%85%E5%90%AB%E5%85%B6%E4%BB%96%E8%BD%AF%E4%BB%B6%EF%BC%8C%E8%BF%99%E4%BA%9B%E8%BD%AF%E4%BB%B6%E5%8F%AF%E8%83%BD%E4%BD%BF%E7%94%A8%E5%85%B6%E4%BB%96%E8%AE%B8%E5%8F%AF%E8%AF%81%EF%BC%88%E5%A6%82%E5%9F%BA%E7%A1%80%E5%8F%91%E8%A1%8C%E7%89%88%E4%B8%AD%E7%9A%84Bash%E7%AD%89%EF%BC%8C%E4%BB%A5%E5%8F%8A%E4%B8%BB%E8%A6%81%E8%BD%AF%E4%BB%B6%E7%9A%84%E7%9B%B4%E6%8E%A5%E6%88%96%E9%97%B4%E6%8E%A5%E4%BE%9D%E8%B5%96%EF%BC%89%E3%80%82%E5%AF%B9%E4%BA%8E%E4%BB%BB%E4%BD%95%E9%A2%84%E6%9E%84%E5%BB%BA%E9%95%9C%E5%83%8F%E7%9A%84%E4%BD%BF%E7%94%A8%EF%BC%8C%E9%95%9C%E5%83%8F%E7%94%A8%E6%88%B7%E6%9C%89%E8%B4%A3%E4%BB%BB%E7%A1%AE%E4%BF%9D%E5%85%B6%E4%BD%BF%E7%94%A8%E7%AC%A6%E5%90%88%E6%89%80%E6%9C%89%E5%8C%85%E5%90%AB%E8%BD%AF%E4%BB%B6%E7%9A%84%E7%9B%B8%E5%85%B3%E8%AE%B8%E5%8F%AF%E8%AF%81%E3%80%82
您可以使用以下命令拉取该镜像。请将 <标签> 替换为具体的标签版本。如需查看所有可用标签版本,请访问 标签列表页面。
来自真实用户的反馈,见证轩辕镜像的优质服务