Running Clash for Docker with configuration tools. Convert Loyalsoldier/clash-rules to clash (GPL version) compatible.
The configuration script is seriously primitive for now. For my own usage habits, this could only accepts trojan links from subscription.
It will set all the proxies in to a single proxy group with method url-test. The config.yaml shall be reconfigured
if needed.
A continer can be run directly from the image on docker hub.
docker run -e SUB_URL=<your_sub_link> -p 7890:7890 -v <path_to_dir>:/configs wuniu/clash-dockerReplace <your_sub_link with your subscription link (which returns aset of base64-encoded
Trojan links). It is also recommended to set -v <path_to_dir>:/configs and replace <path_to_dir>
with a local path to store the generated clash config to enable to change the clash config manually later.
The container will fetch rules from Loyalsoldier/clash-rules converts them for Clash, and combines them with your subscription Trojan links and default settings in config.yaml.
Container won't fetch the rules once the config.yaml have been generated.
Also, the project can be built locally hereafter.
docker build -t clash-build -f Dockerfile.build-clash
docker build -t clash-docker .
docker run -e SUB_URL=<your_sub_link> -p 7890:7890 -v <path_to_dir>:/configs clash-dockerThis will build Clash locally (for AMD64), then run a Docker container. The container will automatically fetch Clash rules, adapt the rules for Clash (GPL version), and run Clash at port 7890.
After the config.yaml has been generated, you could add your rules to it.
- Rules are re-fetched every time the container starts
- An external config solution should be added (But it need to be easier.)
- Currently only supports the url-test proxy group type
- A filter is needed as some subscription links are invalid
- Only supports Trojan links
- The clashtools package cannot be installed for some reason (There is no need for doing this.)
- The code needs refactoring
Wunewww [email protected]