taoziyoyo2566/xray_docker repository overview

⁠Xray Docker Image

Multi-platform Xray images built from official Xray release assets.

⁠Supported platforms

amd64 is the standard Docker/OCI name for the 64-bit x86 platform; it is not limited to AMD processors. Docker automatically selects the matching platform variant when an image is pulled. This image does not publish 32-bit 386 or 32-bit ARM variants.

⁠Tag overview

All versioned tags are immutable. After a versioned tag is published, it is never overwritten or moved to another image digest.

latest is the only moving tag. It points to the newest recommended and verified stable image. Beta images are never assigned to latest.

⁠Stable images

For example, after two image-level improvements to Xray v26.3.27:

latest      -> v26.3.27-r2
v26.3.27-r2    immutable
v26.3.27-r1    immutable
v26.3.27       immutable (implicit r0)

An image revision changes the image packaging, base image, entrypoint, or other repository-owned content without changing the bundled Xray version. Per-release revision overrides are recorded in docker-build/XRAY_IMAGE_REVISIONS.json; releases not listed there use r0.

⁠Beta images

An upstream GitHub release with prerelease=true is published with a -beta suffix in this repository. Here, beta is the repository's concise name for the GitHub prerelease state; it does not claim a more specific upstream release stage.

Beta tags are immutable and never receive a moving alias.

⁠Pulling images

Use latest when automatic stable updates are desired:

docker pull taoziyoyo2566/xray_docker:latest

Use an immutable version tag for controlled upgrades:

docker pull taoziyoyo2566/xray_docker:v26.3.27-r2

For strictly reproducible deployments, pin the verified top-level image digest. A digest remains the authoritative image identity even if a tag is deleted.

⁠Publication and verification

Images are pushed without a public tag, verified on both supported platforms, and only then assigned their immutable version tag. Stable publication also moves latest to the verified digest. Publication refuses to continue when the target version tag already exists.

Missing version tags may be restored only from their recorded, independently verified digest; latest is never used to guess a missing revision. An existing version tag is never repaired by moving it to different content.