Docker-UrNetwork Releases v2025.9.12-728916620

A minimal Docker setup that automatically fetches, updates, and runs the latest urNetwork Provider. The container is built on Alpine Linux, ensuring a minimal footprint. Includes built-in authentication handling, resilient restarts, scheduled in-container updates, and network diagnostics.

Features

• Automated retrieval of the latest urNetwork Provider binary on startup
• Secure credential management via environment variables
• Alpine-based image for minimal footprint
• Persistent storage of authentication tokens and version metadata
• Scheduled update watcher (default at 12:00 Asia/Manila)
• Resilient provider execution with automatic retries and re-authentication
• Built-in network diagnostic script (ipinfo.sh)

Prerequisites

• Docker Engine
• A valid urNetwork account (USER_AUTH and PASSWORD)

Run

# Option 1 : amd64 build
docker run -d --platform linux/amd64 \
  --name="urnetwork-main" \
  --restart="always" \
  --pull="always" \
  --cap-add NET_ADMIN \
  -e USER_AUTH="[email protected]" \
  -e PASSWORD="YourPassword" \
  -v /path/to/your/proxy.txt:/app/proxy.txt \
  -v vnstat_data:/var/lib/vnstat \
  -p 8080:8080 \
  ghcr.io/techroy23/docker-urnetwork:latest

# Option 2 : arm64 build
docker run -d --platform linux/arm64 \
  --name="urnetwork-main" \
  --restart="always" \
  --pull="always" \
  --cap-add NET_ADMIN \
  -e USER_AUTH="[email protected]" \
  -e PASSWORD="YourPassword" \
  -v /path/to/your/proxy.txt:/app/proxy.txt \
  -v vnstat_data:/var/lib/vnstat \
  -p 8080:8080 \
  ghcr.io/techroy23/docker-urnetwork:latest

• (Optional) Mount a proxy configuration file from host to container.
• Replace /path/to/your/proxy.txt with the absolute path on your host.
• Inside the container it will appear at /app/proxy.txt for automatic detection.
• Omit this line entirely if you don't want to use a proxy.
• Stats JSON Portal = http://localhost:port/cgi-bin/stats
• About -v vnstat_data:/var/lib/vnstat and -p 8080:8080
• The -v vnstat_data:/var/lib/vnstat flag mounts a named Docker volume called vnstat_data to /var/lib/vnstat inside the container. /var/lib/vnstat is where vnstat stores its traffic database.
• Mounting it ensures your bandwidth history persists across container restarts or image updates.
• If you run multiple containers, each one needs its own separate vnstat database volume and port to avoid overwriting each other’s stats.
• For example:
• -v vnstat_data1:/var/lib/vnstat # for first container
• -p 9001:8080 # Host port 8081 # for first container
• -v vnstat_data2:/var/lib/vnstat # for second container
• -p 9002:8080 # Host port 9000 # for second container

Promo Video

Promo

• [ REGISTER HERE ]