MicroWARP
🚀 An 800KB RAM ultra-lightweight Cloudflare WARP SOCKS5 proxy in Docker. 仅需 800KB 内存的纯内核态 Cloudflare WARP 代理 - Docker
Runs with mockssource: GitHubShellMITcommit 82a4c62042fb
Shell, MIT licensed. The project labels itself: alpine, bypass dpi, cloudflare, cloudflare warp, docker, lightweight, proxy and socks5.
MicroWARP runs, with stand-ins for the services it depends on. An Argusic agent installed it in 15 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
microsocks SOCKS5 proxy built from source and verified with real traffic, usque v4.2.1 binary extracted and registered with real Cloudflare WARP MASQUE API, entrypoint script passes shellcheck and runs both WireGuard and MASQUE paths end-to-end through real WARP registration into listening SOCKS5 proxies
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 46 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- Docker daemon not available in container (no root, no rootlesskit support without slirp4netns)8 minutes
- WireGuard kernel module not loaded and mock wg-quick/ip used for kernel-level operations2 minutes
- Cannot mkdir /etc/wireguard (no root)2 minutes
- Install time
- 15 minutes
- Cold machine to finish
- 16 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- curl -sS --proxy socks5://127.0.0.1:10994 http://httpbin.org/ip returned origin 213.173.111.110 (200); entrypoint WireGuard path: real wgcf registration generated /tmp/wireguard-workdir/wg0.conf, microsocks started on 127.0.0.1:10990 with auth; entrypoint MASQUE path: real usque registration generated masque-config.json, l4-socks listening on port 10993; SOCKS5 handshake verified (0500 no-auth, 0502+0100 auth)
- Model tokens used
- 199,358
- Exact commit tested
- 82a4c62042fb
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
- Behaviour against real services
- this run was verified against stand-in services only
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
**What was verified:** - **microsocks** built from source (C, ~36KB), runs and proxies real HTTP traffic through SOCKS5 - **usque** v4.2.1 extracted (~13MB), registered with real Cloudflare MASQUE API, got valid credent… - **entrypoint.sh** passes syntax check, runs both WireGuard and MASQUE paths through to SOCKS5 pro… - **wgcf** (v2.3.0) registered with real Cloudflare WARP API, produced valid `wg0.conf` with dual-s… - **SOCKS5 auth** (both no-auth and username/password) verified via handshake - **EGRESS probe** (the entrypoint's `curl cdn-cgi/trace`) returned a real IPv4 address - Test mode (`MICROWARP_TEST_MODE=1`) exits cleanly **What could not be fully verified end-to-end:** - The WireGuard kernel tunnel (`wg-quick up`) needs NET_ADMIN + wireguard.ko (requires Docker) - The MASQUE QUIC tunnel needs UDP connectivity (tested in environment that allowed it to register … - Docker build (`docker build`) not possible without Docker daemon
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Installed in 15 minutes.
- Recovered from all 3 errors without a human stepping in, which says the failures are documented well enough to solve.
- Licensed MIT, as reported by its host.
- Measured 2 times, so the result is not a one-off.
What did not, or is not known
- Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 2/3 | Runs with mocks | 92.00 | 0.07 | |
| Argusic Runner | 1/3 | Did not run | 0.00 | 0.23 |
Topics (from GitHub)
alpinebypass-dpicloudflarecloudflare-warpdockerlightweightproxysocks5warpwireguardzero-trust
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/microwarp)Questions
- Does MicroWARP run?
- MicroWARP runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 15 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test MicroWARP?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 82a4c62042fb. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test MicroWARP?
- The run that produced this verdict cost $0.07: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does MicroWARP take to install?
- 15 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does MicroWARP need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing MicroWARP?
- 3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for MicroWARP?
- All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.