epicmorg/p4p repository overview

⁠epicmorg/p4p

The Perforce Helix proxy (p4p) as a container: built FROM epicmorg/perforce:<release>⁠ on Debian 13 trixie, runs p4p under tini and caches file content in front of a remote Helix server.

⁠What's inside

• everything from epicmorg/perforce:<release> (the Helix binaries of that release);
• entrypoint that execs p4p -p ${P4PORT} -r ${P4PCACHE} -t ${P4TARGET} -R ${P4PROOT} [-L ${P4LOG}] [-v ${P4DEBUG}] [-v proxy.monitor.level=${P4MONITOR_LEVEL}] [-v proxy.monitor.interval=${P4MONITOR_INTERVAL}] ${P4ARGS} <docker run args> (fails fast when P4TARGET is empty);
• volumes /perforce/cache (file content), /perforce/root (the proxy's own db.*, P4PROOT) and /perforce/logs; port 1666; monitoring on by default (P4MONITOR_LEVEL=3, P4MONITOR_INTERVAL=10, empty = off).

⁠Tags

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

⁠Usage

services:
  p4p:
    image: epicmorg/p4p:r24.2
    restart: unless-stopped
    environment:
      P4TARGET: "ssl:perforce.example.com:1666"
    ports:
      - "1666:1666"
    volumes:
      - p4p-cache:/perforce/cache
      - p4p-logs:/perforce/logs
volumes:
  p4p-cache:
  p4p-logs:

Clients then use the proxy as their P4PORT (p4 -p proxy-host:1666 ...).

⁠Notes

• Use the same release as (or one supported by) your Helix server.

⁠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