EN Docker: Add ghcr.io/xtls/xray-core #693 & Add: Gentoo linux installation #e1e74c5 (#694)

* log.json

* EN Docker: Add ghcr.io/xtls/xray-core

* EN Gentoo
pull/695/head
Meow 2025-06-17 01:24:34 +08:00 committed by GitHub
parent 60a1db478f
commit dbe835d775
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
2 changed files with 42 additions and 6 deletions

View File

@ -105,6 +105,7 @@ ghcr.io/xtls/xray-core 版本映像:
- `/usr/local/bin/xray`Xray 主程序(拥有者是 root:root、文件权限 755
- `/usr/local/etc/xray/`:配置文件目录(挂载点)(拥有者是 root:root、目录权限 755、文件权限 644
- 00_log.json
- 01_api.json
- 02_dns.json
- 03_routing.json

View File

@ -70,16 +70,51 @@ The Linuxbrew package manager is used in the same way as Homebrew: `brew install
### Debian <Badge text="WIP" type="warning"/>
### Gentoo
Currently, three third-party Overlays provide Portage installation scripts:
- **[CHN-beta/touchfish-os](https://github.com/gentoo-mirror/touchfish-os/tree/master/net-proxy/Xray)**: Individually maintained, designed for systemD systems
- **[Gentoo-zh](https://github.com/microcai/gentoo-zh)**: Community-maintained, designed for systemD systems
- **[JuanCldCmt/Xray-Overlay](https://github.com/JuanCldCmt/Xray-Overlay)**: Individually maintained, designed for openRC systems. Runs under the `xray` user group for enhanced security
Use `layman` or `eselect-repository` to add the Overlay to your local repository, then install.
## Install via Docker
- [teddysun/xray](https://hub.docker.com/r/teddysun/xray)
Currently two different styles of Docker images are provided:
### The File Structure of the Docker Image
- [teddysun/xray](https://hub.docker.com/r/teddysun/xray): Root privileges, shell environment, compatible with all architectures supported by Alpine. Compiled and built via a private server (dl.lamp.sh). Offers better ease of use
- [ghcr.io/xtls/xray-core](https://ghcr.io/xtls/xray-core): Rootless, no shell environment, supports more architectures. Compiled from the official repository with build provenance. Sacrifices convenience for extreme security
- `/etc/xray/config.json`: configuration file
- `/usr/bin/xray`: Xray main program
- `/usr/local/share/xray/geoip.dat`: IP data file
- `/usr/local/share/xray/geosite.dat`: domain name data file
### Docker Image File Structure
teddysun/xray image:
- `/usr/bin/xray`: Xray-core executable
- `/etc/xray/config.json`: Single configuration file (its directory is the mount point)
- `/usr/share/xray/`: Resource directory containing v2fly geodata files
- geoip.dat
- geosite.dat
ghcr.io/xtls/xray-core image:
- `/usr/local/bin/xray`: Xray-core executable (owner: root:root, permissions: 755)
- `/usr/local/etc/xray/`: Configuration directory (mount point). Owner: root:root, directory permissions: 755, file permissions: 644
- 00_log.json
- 01_api.json
- 02_dns.json
- 03_routing.json
- 04_policy.json
- 05_inbounds.json
- 06_outbounds.json
- 07_transport.json
- 08_stats.json
- 09_reverse.json
- `/usr/local/share/xray/`: Resource directory containing Loyalsoldier geodata files (same permissions as above)
- geoip.dat
- geosite.dat
- `/var/log/xray/`: Log directory (mount point). Directory owner: root:root, permissions: 755. File owner: 65532:65532, permissions: 600
- access.log
- error.log
# GUI Client