 or a reverse SSH tunnel.
amd64armarm64ppc64x86[!NOTE]
Only the stable toolchain of these architectures is supported.
On the worker node(s), run the containerized distcc server (distccd):
shelldocker run -d -p 3632:3632 --name gentoo-distcc --rm ksmanis/gentoo-distcc:tcp
distccd should now be accessible from all interfaces at port 3632
(0.0.0.0:3632).
[!NOTE]
Only private IP addresses are allowed to connect to distccd by default.
Command-line arguments are passed on verbatim to distccd. For instance, you can turn on the built-in HTTP statistics server:
shelldocker run -d -p 3632-3633:3632-3633 --name gentoo-distcc --rm ksmanis/gentoo-distcc:tcp --stats
The statistics server should now be accessible from all interfaces at port 3633
(0.0.0.0:3633).
For a full list of options refer to distccd(1).
If you share a worker instance between multiple clients, you might be interested
in enabling server-side caching with ccache to avoid redundant recompilations.
To do so, pull the tcp-ccache tag:
shelldocker run -d -p 3632:3632 --name gentoo-distcc-ccache --rm ksmanis/gentoo-distcc:tcp-ccache
The directory /var/cache/ccache automatically persists in an anonymous Docker
volume, but a named Docker volume or a bind mount may also be used for stronger
persistence guarantees.
Ccache statistics can be queried as follows:
shelldocker exec gentoo-distcc-ccache ccache -sv
All amd64 image variants support cross-compilation for the arm64
architecture (specifically the aarch64-unknown-linux-gnu toolchain) and vice
versa: all arm64 image variants support cross-compilation for the amd64
architecture (specifically the x86_64-pc-linux-gnu toolchain). In other words,
an amd64 desktop can be used to cross-compile for an arm64 Raspberry Pi and
vice versa.
Cross-compilation support is enabled out of the box without any user configuration. More architecture combinations can be added upon request.
A manual way to test the containers is to compile a sample C file:
c#include <stdio.h> int main() { printf("Hello, distcc!\n"); return 0; }
shellDISTCC_HOSTS="127.0.0.1:3632" DISTCC_VERBOSE=1 distcc gcc -c main.c -o /dev/null
来自真实用户的反馈,见证轩辕镜像的优质服务
免费版仅支持 Docker Hub 加速,不承诺可用性和速度;专业版支持更多镜像源,保证可用性和稳定速度,提供优先客服响应。
免费版仅支持 docker.io;专业版支持 docker.io、gcr.io、ghcr.io、registry.k8s.io、nvcr.io、quay.io、mcr.microsoft.com、docker.elastic.co 等。
当返回 402 Payment Required 错误时,表示流量已耗尽,需要充值流量包以恢复服务。
通常由 Docker 版本过低导致,需要升级到 20.x 或更高版本以支持 V2 协议。
先检查 Docker 版本,版本过低则升级;版本正常则验证镜像信息是否正确。
使用 docker tag 命令为镜像打上新标签,去掉域名前缀,使镜像名称更简洁。
探索更多轩辕镜像的使用方法,找到最适合您系统的配置方式
通过 Docker 登录认证访问私有仓库
在 Linux 系统配置镜像加速服务
在 Docker Desktop 配置镜像加速
Docker Compose 项目配置加速
Kubernetes 集群配置 Containerd
在宝塔面板一键配置镜像加速
Synology 群晖 NAS 配置加速
飞牛 fnOS 系统配置镜像加速
极空间 NAS 系统配置加速服务
爱快 iKuai 路由系统配置加速
绿联 NAS 系统配置镜像加速
QNAP 威联通 NAS 配置加速
Podman 容器引擎配置加速
HPC 科学计算容器配置加速
ghcr、Quay、nvcr 等镜像仓库
无需登录使用专属域名加速
需要其他帮助?请查看我们的 常见问题 或 官方QQ群: 13763429