Decrease Gentoo compilation times by leveraging spare resources, such as an Ubuntu or Windows box idling around. Docker is the only prerequisite.
- Flexible deployment
- Locally (in a private network)
- Remotely (over the internet)
- Out-of-the-box support for the following Gentoo architectures:
amd64armarm64ppc64x86
Note: Only the stable toolchain of these architectures is currently supported.
distcc can run over TCP or SSH connections. TCP connections are fast but relatively insecure, whereas SSH connections are secure but slower. In a trusted environment, such as a LAN, you should use TCP connections for efficiency; otherwise use SSH connections.
On the worker node(s), run the containerized distcc server (distccd):
docker run -d -p 3632:3632 --name gentoo-distcc-tcp --rm ksmanis/gentoo-distcc:tcpdistccd should now be accessible from all interfaces at port 3632
(0.0.0.0:3632):
$ docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
405bb6e87ce8 ksmanis/gentoo-distcc:tcp "tini -e 143 -- dock…" 2 seconds ago Up 2 seconds 0.0.0.0:3632->3632/tcp gentoo-distcc-tcpCommand-line arguments are passed on verbatim to distccd. For instance, you can turn on the built-in HTTP statistics server:
docker run -d -p 3632-3633:3632-3633 --name gentoo-distcc-tcp --rm ksmanis/gentoo-distcc:tcp --statsThe statistics server should now be accessible from all interfaces at port 3633
(0.0.0.0:3633):
$ docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
4e553e359782 ksmanis/gentoo-distcc:tcp "tini -e 143 -- dock…" 3 seconds ago Up 2 seconds 0.0.0.0:3632-3633->3632-3633/tcp gentoo-distcc-tcpFor a full list of options refer to distccd(1).
On the worker node(s), run the containerized SSH server (sshd):
docker run -d -p 30022:22 -e AUTHORIZED_KEYS="..." --name gentoo-distcc-ssh --rm ksmanis/gentoo-distcc:sshsshd should now be accessible from all interfaces at port 30022
(0.0.0.0:30022):
$ docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
5aa87c1eaf59 ksmanis/gentoo-distcc:ssh "docker-entrypoint.sh" 3 seconds ago Up 2 seconds 0.0.0.0:30022->22/tcp gentoo-distcc-sshInstead of including the public key verbatim in the above command, you may prefer to read it from a file on the Docker host:
docker run -d -p 30022:22 -e AUTHORIZED_KEYS="$(cat /path/to/key.pub)" --name gentoo-distcc-ssh --rm ksmanis/gentoo-distcc:sshCommand-line arguments are passed on verbatim to sshd. For a full list of options refer to sshd(8).
The SSH server allows only public key authentication. More specifically, only
the distcc-ssh user is accessible with the public key provided with the
required AUTHORIZED_KEYS environment variable. The username is configurable
through the optional SSH_USERNAME environment variable:
docker run -d -p 30022:22 -e SSH_USERNAME=bob -e AUTHORIZED_KEYS="..." --name gentoo-distcc-ssh --rm ksmanis/gentoo-distcc:sshA manual way to test the containers is to compile a sample C file:
#include <stdio.h>
int main() {
printf("Hello, distcc!\n");
return 0;
}DISTCC_HOSTS="127.0.0.1:3632" DISTCC_VERBOSE=1 distcc gcc -c main.c -o /dev/nullDISTCC_HOSTS="@localhost-distcc" DISTCC_VERBOSE=1 distcc gcc -c main.c -o /dev/nullThe localhost-distcc host should be properly set up in your ~/.ssh/config:
Host localhost-distcc
HostName 127.0.0.1
Port 30022
User distcc-ssh
IdentityFile ~/.ssh/distcc
StrictHostKeyChecking noNote: StrictHostKeyChecking no is required in the above configuration
because the host keys of the container are automatically regenerated upon
execution, if missing. If you wish to eliminate this potential security issue,
you should store the host keys in a volume and mount them upon execution so that
they are not regenerated.
![dependabot[bot] avatar](https://avatars.githubusercontent.com/in/29110?v=4 "dependabot[bot]")
![renovate[bot] avatar](https://avatars.githubusercontent.com/in/2740?v=4 "renovate[bot]")
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent