Repository navigation
Docker Sources
English | 简体中文
Two settings serve different downloads: the package repository installs Docker Engine/buildx; a Docker Hub registry mirror supplies container base images used to build rootfs. Defaults use Docker's official package source and leave the host's Docker image-source configuration unchanged. On a new host, that means official Docker Hub.
Complete-mode terminal installation asks for both settings. Press Enter to keep defaults. In non-interactive mode:
sudo bash /tmp/llmoj-install.sh --repository houyhlouis/LLMOJ \
--yes --docker-source https://YOUR_PACKAGE_MIRROR/docker-ce \
--docker-mirrors https://YOUR_DOCKER_HUB_MIRRORUse only HTTPS URLs without credentials/query strings. Multiple Hub mirrors use commas. Example URLs above are placeholders, not operating public mirrors.
| Option | Expected URL |
|---|---|
--docker-source |
Base such as https://download.docker.com; installer adds /linux/ubuntu
|
--docker-mirrors |
Docker Hub pull-through endpoint, such as https://mirror.example.com
|
Do not append /linux/ubuntu to the package-source option. The custom repository must carry Docker's signed Ubuntu packages for your version. The GPG key is still downloaded from https://download.docker.com/linux/ubuntu/gpg, preserving the official trust key. Existing Docker is not replaced by this option. See Docker's Ubuntu repository instructions.
When rootfs must be built and custom mirrors are selected, the installer merges registry-mirrors into /etc/docker/daemon.json, preserves unrelated settings, validates the candidate with dockerd --validate, backs up the previous file as daemon.json.llmoj-backup-<UTC timestamp>, and applies the change atomically. Invalid JSON/configuration stops before replacement. A changed configuration restarts Docker and may interrupt existing containers.
Blank mirror input leaves daemon.json unchanged. Web-only installation and reuse of an existing rootfs skip Docker setup. Selecting a different mirror/source on a retry conflicts with recorded installation options; reuse the original options, or perform an explicit configuration migration after installation.
Rootfs builds use the local Docker default builder so daemon mirror settings apply. The original rootfs recipe and pinned base-image digest are retained. Mirrors do not accelerate Ubuntu snapshots, GitHub, npm or language downloads; configure those separately if needed. Docker Hub pull-through mirrors also do not mirror arbitrary third-party registries. See Docker's mirror documentation.
For manual judge setup, install Docker from a repository suited to your server and then, if desired, configure the mirrors with the same helper:
sudo python3 deploy/docker-support.py --mirrors https://YOUR_DOCKER_HUB_MIRROR --configureIt prints changed or unchanged. If changed, restart Docker before building; if unchanged, start it if needed. Then use the default builder:
sudo systemctl restart docker # Only when mirror configuration changed.
sudo env BUILDX_BUILDER=default bash deploy/sandbox/build.sh buildKeep the previous Docker backup when planning rollback. This helper never prints private host configuration.
简体中文
- LLMOJ Wiki
- AI 运行环境变量与固定限制
- AI 配置、权限与执行流程
- 后端配置完整参考
- 团队、题解、作废、Hack 与自测升级
- 配置总览与生效规则
- 比赛赛制
- 分布式评测与网页分离
- Docker 源
- 环境变量、构建与维护工具
- 前端与 bootstrap 配置
- HTTPS 与反向代理
- Hack
- 安装与端口配置
- 评测端完整配置与 CPU 扩缩容
- 基础服务与安装后运维配置
- 发布源码、版本与 GitHub Wiki
- 新用户注册审核
- 独立评测机安装
- Self Eval(NOI / OI 比赛预测试)
- 题解
- 评测记录 Fake
- 评测记录预览
- 团队
- 两步验证
- 保留配置与数据的一键升级
English
- LLMOJ Wiki
- AI configuration, permissions and execution
- AI runtime environment and fixed limits
- Complete backend configuration reference
- Teams, solutions, moderation, Hack and self-evaluation upgrade
- Configuration overview and activation
- Contest rules
- Distributed judging and web/judge separation
- Docker sources
- Environment, builds, and maintenance tools
- Frontend and bootstrap configuration
- HTTPS and reverse proxies
- Hacks
- Installation and ports
- Complete judge configuration and CPU resizing
- Infrastructure and post-install operations
- Source, release and GitHub Wiki publishing
- Registration approval
- Independent judge installation
- Self Eval for NOI / OI contests
- Solutions
- Fake submission moderation
- Submission previews
- Teams
- Two-factor sign-in
- Upgrading while preserving configuration and data