epicmorg/perforce repository overview

⁠epicmorg/perforce

Perforce Helix Core binaries for one release per tag, on epicmorg/debian:trixie⁠. A base image: it has no entrypoint and starts nothing by itself - build your own server, broker or proxy image on top of it (see epicmorg/p4p⁠).

⁠What's inside

The official Linux x86_64 binaries of the tagged release from filehost.perforce.com, in /usr/bin:

• p4 (client), p4d (server), p4broker, p4p (proxy), perfmerge, perfsplit;
• older releases also p4ftpd; newer ones also p4dctl, p4migrate, p4mon-prometheus-exporter.

Working directory: /perforce. Each binary path is also exported (P4_BIN, P4D_BIN, P4P_BIN, …).

⁠Tags

Every tag is pushed to docker.io, quay.io and ghcr.io (epicmorg/perforce:<tag> on each) - same digest everywhere.

⁠Usage

FROM epicmorg/perforce:r24.2
# your p4d / p4broker setup, entrypoint, volumes ...

docker run --rm epicmorg/perforce:r24.2 p4 -V

⁠Notes

• Tags are Perforce release names (r16.2 … r26.1); each one downloads that release's binaries.

⁠Links

• Source: EpicMorg/docker⁠ - issues and PRs welcome
• Tags float and are rebuilt weekly; pin by digest for reproducible builds: Tags, pinning and updates⁠
• CHANGELOG⁠ - License: MIT